What's the (technical) purpose of adding t/seaside/ to thepath(was: Re: [Seaside] how to remove '/seaside/someApp')

Sebastian Sastre ssastre at seaswork.com
Thu Aug 16 19:46:37 UTC 2007


ONLY SQUEAK WITH COMANCHE:
here I sending the hack described by Ron Teitelbaum in 07/20/2007 in the
form of a monticello package.
Take it as what it is: a hack
I'm testing it myself, so I don't know anythig yet about to have it in
production

Cheers,

Sebastian Sastre

> -----Mensaje original-----
> De: seaside-bounces at lists.squeakfoundation.org 
> [mailto:seaside-bounces at lists.squeakfoundation.org] En nombre 
> de Carl Gundel
> Enviado el: Sábado, 21 de Julio de 2007 22:10
> Para: Seaside - general discussion
> Asunto: Re: What's the (technical) purpose of adding 
> t/seaside/ to thepath(was: Re: [Seaside] how to remove 
> '/seaside/someApp')
> 
> I host my site behind Apache, but not every developer wants 
> or needs to use Apache or any other front-end, and there's 
> absolutely no good deployment reason to not permit the 
> developer to specify a short path.  Let the developer 
> determine the requirement one way or the other.  If adding 
> this capability involves difficult development work, well 
> then that's a different matter.
> 
> So while I do use Apache and URL rewriting for my public 
> site, I have a need for the short path option with a version 
> of my Seaside based software which I plan to distribute.
> 
> -Carl Gundel
> http://www.runbasic.com
> 
> ----- Original Message -----
> From: "Ching de la Serna" <ching.dls at gmail.com
> >I suppose this might depend on the router that you have. On 
> my router, 
> >I  only set port forwarding to redirect port 80 to my proxy server.  
> >There  are  firewall settings which I don't think is relevant to the 
> >problem at hand.
> > I
> > do not see anywhere I can append '/seaside/myApp' so that my proxy 
> >will do  the right re-direction. A problem might arise when I have 
> >another  application that uses the same router and backend servers. 
> >Would I be able  to do stuff on the router side to get the 
> same results?
> >
> > Ching
> >
> > On 7/20/07, Stephan Eggermont <stephan at stack.nl> wrote:
> >>
> >> On Fri, Jul 20, 2007 at 11:09:50AM +0200, 
> >> seaside-request at lists.squeakfoundation.org wrote:
> >> > From: "Philippe Marschall" <philippe.marschall at gmail.com> 
> >> > 2007/7/19, Ching de la Serna <ching.dls at gmail.com>:
> >> > > Hi,
> >> > >
> >> > > I have a little problem. How do I remove 
> '/seaside/someApp'  such 
> >> > > that
> >> I
> >> > > could have: 'http://someDomain.com/' instead of '
> >> > > http://someDomain.com/seaside/someApp'. Help anyone?
> >> >
> >> > The short answer is you can't. The long answer is if you 
> run behind 
> >> > Apache 2 (which is a good idea) you can use mod_rewrite 
> to hide it.
> >>
> >> If you're behind a router/firewall you can hide it there 
> so you only 
> >> have the /seaside/someApp internally.
> >>
> >> Stephan
> >> _______________________________________________
> >> Seaside mailing list
> >> Seaside at lists.squeakfoundation.org
> >> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
> >>
> >
> 
> 
> --------------------------------------------------------------
> ------------------
> 
> 
> > _______________________________________________
> > Seaside mailing list
> > Seaside at lists.squeakfoundation.org
> > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
> > 
> 
> 
> _______________________________________________
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
-------------- next part --------------
A non-text attachment was scrubbed...
Name: SP-sas.2.mcz
Type: application/octet-stream
Size: 1168 bytes
Desc: not available
Url : http://lists.squeakfoundation.org/pipermail/seaside/attachments/20070816/6b4b6ee2/SP-sas.2.obj


More information about the seaside mailing list