Just to  clarify - each 'yoursitename' is part of the same app - it could be
'youusername' or 'yourorganisation' depending on the app.  e.g. see github's
url structure:
https://github.com/isotoma/ <https://github.com/isotoma/yaybu>

<https://github.com/isotoma/yaybu>isotoma is the 'username' or
'yoursitename' - it's top level but user chosen.  They also have reserved
URLs like:

https://github.com/plans

On 21 March 2011 21:51, VP <vtp2...@gmail.com> wrote:

> 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!)
>

Reply via email to