I'm a bit new to Rails (although, not as new to Ruby), and I'm pretty excited
Slightly before this, however, I thought I'd implement an internal app that we
could use at my company. I'm sending this mail to ask if Rails would be best
suited for this.
We run a hosting business, with some 50 clients. Each client has can have one
or more sites, which each has:
- an Apache VHost
- various email config files
- MySQL databases
- htaccess usernames
- DNS entries
- backup entries
...and so on. There are a lot more.
I've tired of keeping these in sync, so I thought to myself, I'll write a Ruby
script to pull all the info from a database, change some of it, or calculate
some more info as require, and write all of it to a whole bunch of different
files in different places.
Then, I realized, it'd be nice if there were a web frontend to all this, and,
the information somewhat naturally fits an MVC architecture. I decided to
look into using Rails.
So, my actual questions (kudos, you've read this far!) are:
How can I use dynamic scaffolding for all these models? Do I need a separate
controller for each one? I'm fine with the interface generated by the
dynamic scaffold, and i want to focus on the functionality and beckend before
I focus on the interface.
What is the correct, Rails way of generating all those files? They are in
many different places. Perhaps, I can define a view type (I.E., in addition
to HTML, XML, and JS), and then write a helper script to pipe the contents of
a bunch of into files? Or, is there a better way?
Is Rails even the best tool for something like this?
Answers, or advice of any kind, is appreciated!