[Seaside] Seaside paths configuration

[John Toohey]

You should not hardcode you resource paths like this. Replace them with
relative URLs and then configure Apache to server them directly from port
80. You Seaside app can then be configured to run on port 8080, and you can
allow Apache to handle  finding the correct locations. I wrote a little
about this using Apache 2 at the weekend here, http://parspro.blogspot.com/


On Wed, Jun 24, 2009 at 15:08, Sebastian Van Lacke <
svanlacke at caesarsystems.com> wrote:

>  Hi, I need help with Seaside's configuration. I have hardcoded all the
> paths to files that are served by Apache. For example:
>
>
>
> updateRoot: aRoot
>     super updateRoot: aRoot.
>     aRoot stylesheet url: '
> http://192.168.1.10/storyevaluator/css/editingStory.css'
>
>
>
> Now I have to move to other host, and first I should resolve this with
> relatives paths. What is the correct way to do it?
>
> I suppose is setting the configuration paths (resource base url, server
> hostname, and server paths), but every time I touch those paths, my
> application breaks.
>
>
>
> Someone could explain how to use its.
>
>
>
> Thanks!!
>
>
>
> Sebastian
>
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
>


-- 
-JT
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20090624/e429ef77/attachment.htm