[isf-wifidog] UI + usecase suggestions for Wifidog portal pages
mina at naguib.ca
Jeu 20 Oct 10:22:42 EDT 2005
We can avoid the pollution on the main domain by having all these in
I missed the earliest part of the conversation, what is this for to
begin with :) ?
(sorry, the lists' volume is a bit high nowadays)
On 20-Oct-05, at 9:59 AM, Philippe April wrote:
> It's do-able and no maintenance if we do it with a catch-all like
> you said and like I mentionned before, but I'd hate to have
> *.ilesansfil.org (personal choice).
> Mike, put that on your wishlist for wifidog auth.
> Philippe April
> GnuPG http://key.philippeapril.com
> On 20-Oct-05, at 9:35 AM, Scott Tully wrote:
>>> The sub-domain thing can be done easily with apache, but I find it's
>>> a lot of management.
>>> For every new hotspot, create a DNS entry, create an apache
>>> etc. All manually.
>>> If we put *.ilesansfil.org we can touch everything but I don't find
>>> it clean, unless we buy a new domain just for that, in my head it
>>> would just POLLUTE .ilesansfil.org.
>> If you compiled apache with vhost_alias_module it's almost zero
>> maintenance. You would just need to create directories.
>> <VirtualHost ilesansfil.org:80>
>> ServerAlias *.ilesansfil.org
>> ServerAdmin webmaster at ilesansfil.org
>> ServerName www.ilesansfil.org
>> UseCanonicalName Off
>> VirtualDocumentRoot /var/www/%1/public_html
>> You'll need a couple vhosts before this one to catch your www, etc..
>> This should work if you are serving content, otherwise you may be
>> to mod_rewrite your way to a redirect.
>> WiFiDog mailing list
>> WiFiDog at listes.ilesansfil.org
> WiFiDog mailing list
> WiFiDog at listes.ilesansfil.org
More information about the WiFiDog