Re: Web application architecture (subdomain vs. sub directory)
| From: | Per Jessen | Date: | Thu, 26 Aug 2010 06:59:15 +0000 |
| Subject: | Re: Web application architecture (subdomain vs. sub directory) | ||
| References: | 1 2 3 4 5 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-307682@lists.php.net to get a copy of this message | ||
Peter Lind wrote:
> On 26 August 2010 08:08, Per Jessen <per@computer.org> wrote:
>> Tim Martens wrote:
>>
>>> Thanks for all your answers. To clarify my question, I'm looking for
>>> advice regarding how best to set up users for a web app, e.g.,
>>> username.myapp.com vs myapp.com/username and the pros and cons of
>> each.
>>
>> Using username.myapp.com means defining that name in your DNS and
>> having a separate virtual host definition in your apache config.
>>
>
> While offtopic and nothing to do with PHP I think this should be
> corrected: you can set a *.yourdomain rule which matches all
> subdomains not explicitly set. So no, you do not need to define every
> single name as a DNS record.
Good point. Not sure I would personally want to use wildcards, but it's
perfectly valid.
--
Per Jessen, Zürich (17.7°C)