[isf-wifidog] UI + usecase suggestions for Wifidog portal pages

[Philippe April]

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 redirect,
>> 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
> </VirtualHost>
>
> 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 able
> to mod_rewrite your way to a redirect.
>
> Scott
> _______________________________________________
> WiFiDog mailing list
> WiFiDog at listes.ilesansfil.org
> http://listes.ilesansfil.org/cgi-bin/mailman/listinfo/wifidog
>
>