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

[Michael Lenczner]

there's no way in hell either of those solutions would work

*.subdomain.ilesansfil.org

or

*.otherdomain.org.

No one would use it or remember it.

Sometimes we have to do things in an ugly way, even if technically
it's not perfect.  And manually creating a new subdomain each time
can't be *that* difficult for each new hotspot.  Would it take more
than 15 min?  Would that be worth it as an organization to have people
checking out portal pages from home?

 But i don't understand the issue well enough.  Phil - you can explain
to me the technical reluctance next time I see you.

On 10/20/05, Philippe April <isf_lists at philippeapril.com> wrote:
> Yeah I did mention that.
>
> If we're going to have this, my preference would be that we either
> buy a new domain, or use a subdomain for it even if it lenghtens the
> thing a little...
>
> Philippe April
> GnuPG http://key.philippeapril.com
>
> On 20-Oct-05, at 10:22 AM, Mina Naguib wrote:
>
> >
> > We can avoid the pollution on the main domain by having all these
> > in a subdomain
> >
> > *.foo.ilesansfil.org
> >
> > 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
> >>>> 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
> >>>
> >>>
> >>>
> >>>
> >>>
> >>
> >> _______________________________________________
> >> WiFiDog mailing list
> >> WiFiDog at listes.ilesansfil.org
> >> http://listes.ilesansfil.org/cgi-bin/mailman/listinfo/wifidog
> >>
> >>
> >
> >
> > _______________________________________________
> > WiFiDog mailing list
> > WiFiDog at listes.ilesansfil.org
> > http://listes.ilesansfil.org/cgi-bin/mailman/listinfo/wifidog
>
>
>
> _______________________________________________
> WiFiDog mailing list
> WiFiDog at listes.ilesansfil.org
> http://listes.ilesansfil.org/cgi-bin/mailman/listinfo/wifidog
>
>