No it doesn't sound like Dmytrii want's a single instance per client, but it was just a suggestion if he wanted to go that route for better isolation/separation per client site. Obviously it's going to cost a lot more for the amount of servers/RAM you're going to need for all the Rails instances but it's an option. If there is going to be a large number of clients I would think a multi-tenant approach would be better.
Just my two-penneth. On Sep 6, 11:34 am, Warren Seen <[email protected]> wrote: > If you're spinning up a new instance for each client, it's not really > multi-tenanted and this is the approach I'd suggest, but from the way Dmytrii > described it (ie using subdomains), it doesn't sound like this is the way > he's doing it? > > On 06/09/2011, at 8:21 PM, Steve Hodgkiss wrote: > > > > > > > > > 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. -- 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.
