You know the problem. You are agile like hell. You don’t bother doing complicated diagrams to show somebody what you’re doing. That’s okay. But sometimes, you need to show off what you’ve been struggling with, and if that day comes, this little rakefile can save some time.

Simply , Unpack this file ( tar bz btw ) in your rails app’s root folder and call rake db:superdumper. This will create a file called database.dot in your root folder, containing your database scheme, including associations, in the so-called “dot” format, used by the open-source GraphViz package as input. If you don’t have that package, install it, via ports or apt or whatever applies to your platform. 

In Detail what you have to do is here ( assuming you unpacked the file already.. )
 

rake db:superdumper

This task will automatically dump your scheme and call GraphViz, resulting in a pdf file in the root of your app with the name database.pdf. If it’s not your database schema smiling at you, let me know.

You know the problem. You are agile like hell. You don't bother doing complicated diagrams to show somebody what you're doing. That's okay. But sometimes, you need to show off what you've been struggling with, and if that day comes, this little rakefile can save some time. Simply , Unpack this file ( tar bz btw ) in your rails app's root folder and call rake db:superdumper. This will create a file called database.dot in your root folder, containing your database scheme, including associations, in the so-called "dot" format, used by the open-source GraphViz package as input. If you don't have that package, install it, via ports or apt or whatever applies to your platform.  In Detail what you have to do is here ( assuming you unpacked the file already.. )   rake db:superdumper This task will automatically dump your scheme and call GraphViz, resulting in a pdf file in the root of your app with the name database.pdf. If it's not your database schema smiling at you, let me know.