I think each "yoursitename" should be a different app. I think it's most efficient that way.
On Mar 21, 4:37 pm, Tom Atkins <minkto...@gmail.com> wrote: > I am designing an app with a URL structure like this: > > myapp.com/yoursitename > > 'yoursitename' is effectively an argument as there could be many sites and > users are allowed to create their own sites. But I'd like it to be 'top > level'. > > Then within yoursitename there will be URLs like this: > > myapp.com/yoursitename/dashboard > myapp.com/yoursitename/users > myapp.com/yoursitename/settings > > I have a black-list of reserved top level words (e.g. /admin /about /faq > /account etc) that are not allowed to be chosen. So the site will have > controllers to expose pages like: > > myapp.com/faq > myapp.com/about > > My question is what's the best / most efficient way to serve /yoursitename > and the associated controllers? > > (I hope that makes sense!)
