You'd need to use a custom model method to retrieve the object of the user.
The route would simply pass the request parameter with the user id (or
username) that comes from the URL. Of course, you can create a normal route
with a parameter like /:user_id but the idea of using a subdomain per user
i
Yep, I get the wild card thing; just figured its another whole layer
of stuff that I'd prefer not to include.
But what I don't get; is that at some point doing it that way; you
still have to filter out the listing of records to just the ones that
have image.user_id = ?. In your idea, where would t
It depends on the options of your hosting I guess. If you have a panel like
cPanel (even with a shared hosting), you can set a new subdomain with a
wildcard "*" to point directly to your root public folder, and that's it. If
it's still a problem, you could directly create a url pattern adding the
u
Thanks for the suggestion Gustavo, but this seems like way too much
complication for what seems like a pretty simple job; involving DNS
into this potentially adds another whole area for complications and
issues.
can anyone shed some light?
cheers
On Aug 9, 2:36 pm, Gustavo Adrian wrote:
> Maybe
