# Rails applications deployed as subdomains of Rails applicati

**URL:** <https://www.ruby-forum.com/t/rails-applications-deployed-as-subdomains-of-rails-applicati/91113>\
**Category:** Rails\
**Created:** [April 4, 2007, 8:54pm UTC](https://www.ruby-forum.com/t/rails-applications-deployed-as-subdomains-of-rails-applicati/91113 "2007-04-04T20:54:54Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![wpwood](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/w/d6d6ee/32.png) [@wpwood](https://www.ruby-forum.com/u/wpwood)\
**Post date:** [April 4, 2007, 8:54pm UTC](https://www.ruby-forum.com/t/rails-applications-deployed-as-subdomains-of-rails-applicati/91113/1 "2007-04-04T20:54:54Z")

</div>

Sorry about the subject line, but I couldn’t think of a better way to  
state my problem.

I’ve got a Rails app deployed at [www.main-domain.com](http://www.main-domain.com). I need to deploy  
copies of that app to subdomains like [sub1.main-domain.com](http://sub1.main-domain.com),  
[sub2.main-domain.com](http://sub2.main-domain.com), etc. Each subdomain could use the same app code,  
but each _must_ have it’s own database. (They also need their own  
images, stylesheets, etc.) None of the examples I’ve been able to  
Google up have that characteristic. They all assume a shared database  
with the subdomain’s data being filtered in the model. I would really  
appreciate any thoughts / experience / pointers to stuff I’ve missed in  
my Googling that might put me on the right track.

Thanks,  
Bill

---

<div class="post-metadata">

**Author:** ![wpwood](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/w/d6d6ee/32.png) [@wpwood](https://www.ruby-forum.com/u/wpwood)\
**Post date:** [April 5, 2007, 6:07am UTC](https://www.ruby-forum.com/t/rails-applications-deployed-as-subdomains-of-rails-applicati/91113/2 "2007-04-05T06:07:48Z")

</div>

Bill W. wrote:

> I’ve got a Rails app deployed at [www.main-domain.com](http://www.main-domain.com). I need to deploy  
> copies of that app to subdomains like [sub1.main-domain.com](http://sub1.main-domain.com), [sub2.main-domain.com](http://sub2.main-domain.com),  
> etc. Each subdomain could use the same app code, but each _must_ have it’s  
> own database. (They also need their own images, stylesheets, etc.) None of the  
> examples I’ve been able to Google up have that characteristic. They all assume  
> a shared database with the subdomain’s data being filtered in the model. I would  
> really appreciate any thoughts / experience / pointers to stuff I’ve missed in my  
> Googling that might put me on the right track.

Since you _must_ have own database as a requirement the simplest  
solution is to deploy one app for each sub-domain. You can use Virtual  
Host  
to set this up.

The down side is code maintenance can get complicated.

– Long  
[http://MeandmyCity.com/](http://MeandmyCity.com/) - Find your way  
[http://edgesoft.ca/blog/read/2](http://edgesoft.ca/blog/read/2) - No-Cookie Session Support plugin