# Ruby on Rails: Talk | Google Groups

**URL:** <https://www.ruby-forum.com/t/ruby-on-rails-talk-google-groups/160085>\
**Category:** Rails\
**Created:** [February 11, 2009, 5:13pm UTC](https://www.ruby-forum.com/t/ruby-on-rails-talk-google-groups/160085 "2009-02-11T17:13:46Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Heinrich\_Beck](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/h/fbc32d/32.png) [@Heinrich\_Beck](https://www.ruby-forum.com/u/Heinrich_Beck)\
**Post date:** [February 11, 2009, 5:13pm UTC](https://www.ruby-forum.com/t/ruby-on-rails-talk-google-groups/160085/1 "2009-02-11T17:13:46Z")

</div>

This is more an architectural question…

I am looking to create a domain that sells widgets (as an example)

[widgets.com](http://widgets.com)

Now I have three sales reps, that each sell different kinds of  
widgets, and do not need to know about each other.

[larry.widget.com](http://larry.widget.com)

[moe.widget.com](http://moe.widget.com)

[curley.widget.com](http://curley.widget.com)

I don’t want to repeat myself (of course!) with the shopping cart  
logic or the transactional logic.

So, should I simply make a view for each user and then direct the  
requests to the appropriate view? or is there a better way of doing  
this?

---

<div class="post-metadata">

**Author:** ![Heinrich\_Beck](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/h/fbc32d/32.png) [@Heinrich\_Beck](https://www.ruby-forum.com/u/Heinrich_Beck)\
**Post date:** [February 11, 2009, 6:54pm UTC](https://www.ruby-forum.com/t/ruby-on-rails-talk-google-groups/160085/2 "2009-02-11T18:54:57Z")

</div>

Have you looked at the Railscast on subdomains?

> **[\#123 Subdomains - RailsCasts](http://railscasts.com/episodes/123-subdomains)**
>
> Short Ruby on Rails screencasts containing tips, tricks and tutorials. Great for both novice and experienced web developers.

Eifion

> **[ASCIIcasts - Recent Episodes](https://asciicasts.com)**
>
> A variety of short articles about Ruby and Rails based on Ryan Bates’ Railcasts.

Twitter: eifion
