one rails, multiple DBs
Marcelo Barbudas
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.
Marnen Laibow-Koser
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
mar...@marnen.org
--
Posted via http://www.ruby-forum.com/.
Marcelo Barbudas
> 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.
Marnen Laibow-Koser
And all of that would be easier with one big DB, at least as far as
you've described.
>
> --
> Cheers,
> M.
Marcelo Barbudas
>
> > 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.
myobie
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