Ruby on Rails

On Sep 21, 2013, at 6:55 AM, Denny Mueller <macd...@googlemail.com> wrote:

> Ok the situation is that I have an App, where to user can sign in and can use the app save some data like customers and orders to the db.
> Since I'm using devise for authentication, I realised the multitenenacy with current_user in the controller. So every user has his own data.
>
> like
>
>   def index
>     @customers = current_user.customers
>   end
>
> etc
>
> This works fine right now. But yesterday I watched some railscast.
> http://railscasts.com/episodes/389-multitenancy-with-postgresql
> http://railscasts.com/episodes/388-multitenancy-with-scopes
>
> As you can see the first one uses pg schemas and the second one works with scopes. Both have the same effect like my way. But what could be the advantages or disadvantages to these 3 ways? Dont want to build further on my app and realise in the end that I picked the wrong way. Maybe in the end of the app there will be a function user can team up and have shared data... but this is just a nice to have.
>
> Any experince, hints or suggestion on that?
>
> best regards
> denym_

Best suggestion here I can make is pick up Radar's book:

http://www.goodreads.com/book/show/18333875-multitenancy-with-rails

really a great read, very helpful in this.