Thanks for this advice. I have looked into the hosts file, and dnsmasq
options, and I think I may go down the hosts file route. (I know
dnsmasq is designed to be simple, but I think even that is slight
overkill for my needs)
Michal.
On 31 Oct 2009, at 22:48, Simon Thulbourn wrote:
As for the routing, you could do something like this:
<route name="subdomain" pattern="^(subdomain:[^\.]+).(domain:.+)$"
source="_SERVER[SERVER_NAME]" module="Default">
Then if you need to check it exists, you could use a call back.
Simon Thulbourn
On 31 Oct 2009, at 22:45, Mike Seth wrote:
Michal Charemza wrote:
Hi,
I'm hoping to route using subdomains as a source, using (I presume)
the parameter source="_ENV[HTTP_HOST]" in the route. I expect this
to
work fine, except I'm not sure how to test this before going live.
Routing on paths is independent of the server, but this is no longer
the case with routing based on subdomains. I wonder if anyone has
any
advice?
Your development environment will eventually require DNS. It requires
DNS now :) Use a lightweight DNS server/proxy such as dnsmasq (or
if you
work on a single machine, editing the hosts file will do). Setup your
staging environment to reflect the DNS structure on the production
servers. This fits really nicely with Agavi configuration features
_______________________________________________
users mailing list
[email protected]
http://lists.agavi.org/mailman/listinfo/users
_______________________________________________
users mailing list
[email protected]
http://lists.agavi.org/mailman/listinfo/users
_______________________________________________
users mailing list
[email protected]
http://lists.agavi.org/mailman/listinfo/users
