I''ve got a rails project that I would like to duplicate for each of my sites. Rather than aggregating all sites into a single database, I would like to let each site own it''s own database. The reason is that I''m working with inventory and some possibly sensitive accounting information, and I would like total separation between each client''s data. The plan is to keep a master development project, and then to copy the code out to all of the sites. The best way I can think to accomplish this would be to write a ruby file that copies some but not all of each project to a new folder, and then deploy each site. So a new site would be set up using commands like: # rails new_project # script/clone Where script/clone would copy everything from the master development site to the new site except the following files: config log public/images public/stylesheets any file_column folders and then for updates, I guess I would have a ''update_clones.rb'' file somewhere that would push everything except the above files out to all sites. I guess my question is whether there is some system already in place for this. Does Capistrano handle it? There seems to be precious little documentation on Capistrano. I don''t want to reinvent the wheel, but I haven''t heard of anything like this so far. Thanks for any feedback. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk -~----------~----~----~----~------~----~------~--~---