Hi. I''m in a situation where I have to provide a hosted Rails App solution. I''m running Apache with passenger in the backend. What is the proper way to change the DB depending on the subdomain? Should I use data_fabric? -- R. -- 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-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
Marcelo Barbudas wrote:> Hi. > > I''m in a situation where I have to provide a hosted Rails App > solution. I''m running Apache with passenger in the backend. > > What is the proper way to change the DB depending on the subdomain? > Should I use data_fabric?Generally, you don''t need a separate DB for each subdomain. One big DB is usually better.> > -- > R.Best, -- Marnen Laibow-Koser http://www.marnen.org marnen-sbuyVjPbboAdnm+yROfE0A@public.gmane.org -- Posted via http://www.ruby-forum.com/. -- 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-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
Hi,> Generally, you don''t need a separate DB for each subdomain. One big DB > is usually better.It''s a high volume app, that''s written as a standalone service. Extending it as a hosted solution and keeping updates nice is a big part of what the project is about. -- Cheers, M. -- 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-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
Marcelo Barbudas wrote:> Hi, > >> Generally, you don''t need a separate DB for each subdomain. �One big DB >> is usually better. > > It''s a high volume app, that''s written as a standalone service. > Extending it as a hosted solution and keeping updates nice is a big > part of what the project is about.And all of that would be easier with one big DB, at least as far as you''ve described.> > -- > Cheers, > M.Best, -- Marnen Laibow-Koser http://www.marnen.org marnen-sbuyVjPbboAdnm+yROfE0A@public.gmane.org -- Posted via http://www.ruby-forum.com/. -- 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-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
Hi.> > > It''s a high volume app, that''s written as a standalone service. > > Extending it as a hosted solution and keeping updates nice is a big > > part of what the project is about. > > And all of that would be easier with one big DB, at least as far as > you''ve described. >You are right, it would definitely be easier if this App was written with a hosted version in mind. Unfortunately it isn''t. Still, the volume of traffic and DB size of the app means that if someone grows bigger we want to be able to quickly move it to something dedicated. -- Cheers, R. -- 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-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
DataMapper out of the box will let you use multiple databases, although these need to be known at app boot time. For ActiveRecord, this article might lead you somewhere: http://tomayko.com/writings/rails-multiple-connections Nathan On Feb 10, 1:34 pm, Marcelo Barbudas <nos...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> Hi. > > > > > > It''s a high volume app, that''s written as a standalone service. > > > Extending it as a hosted solution and keeping updates nice is a big > > > part of what the project is about. > > > And all of that would be easier with one big DB, at least as far as > > you''ve described. > > You are right, it would definitely be easier if this App was written > with a hosted version in mind. Unfortunately it isn''t. > > Still, the volume of traffic and DB size of the app means that if > someone grows bigger we want to be able to quickly move it to > something dedicated. > > -- > Cheers, > R.-- 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-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.