I have about 25 different domains on it. Not had any issues with the number of domains, but they are part of the app and I don't expect many more to be added, so it makes sense to store everything in version control together.
Other options I can think of would be to manage the templates and assets from an interface using liquid. Or if you want to have a deploy per client you could engine the app and reference it with bundler from a fresh rails app for each client. On Sep 6, 9:15 am, Dmytrii Nagirniak <[email protected]> wrote: > > I did something similar recently, but based on domain rather than > > subdomain. Either way it's easy to add a load path that's based on the > > domain, so views can be overridden on a per site basis. > > Thanks. Useful piece of code :) > I think about similar approach but it feels a bit dirty as each clients look > and feel is going to be under our source control. > > Did you find it hard to manage many domains? Or you just had a fixed number > of those? > > Cheers. -- You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rails-oceania?hl=en.
