Seaside deployment help

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Seaside deployment help

Luc Fabresse
Hi all,

 It is the first time I want to deploy a seaside app and I encouter problems that have already been discussed and blogged but I can't find the needed informations.

 The situation:

    1) On web server ( e.g www.monsite.fr) on which I have an account named luc and no specials rights (root password...)
    2) my web site is accessible through http://www.monsite.fr/~luc/
    3) adding rewriting rules in a .htaccess allows me to redirect request to a backend server on which I have root access :
        http://www.mysite.fr/~luc/seaside/* -> http://myserver:9090/...

 I would :
    configure the seaside image so that all urls will have the following form : /~luc/seaside/*
    (I guess it is the most simple way to achieve my will)
 but I don't want to use the two atributes "Server Hostname" and "Server Path" because I would prefer a simpler solution like modify the default WADispatcher in order to configure all applications at once.
Is there a better solution ?
 
 Questions:
    - What is "Resourse base Url" configuration?
    When I changed it for counter app for example,  static files url are not changer and links are not good e.g
    /seaside/files/WAStandardFiles/toolbar.css

#Luc


_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Reply | Threaded
Open this post in threaded view
|

Re: Seaside deployment help

Lukas Renggli
>     configure the seaside image so that all urls will have the following
> form : /~luc/seaside/*
>     (I guess it is the most simple way to achieve my will)
>  but I don't want to use the two atributes "Server Hostname" and "Server
> Path" because I would prefer a simpler solution like modify the default
> WADispatcher in order to configure all applications at once.
> Is there a better solution ?

What about a one-liner that sets the server-path for all applications?

You don't need to bother about hostname if you use Apache 2, because
Seaside will figure out by itself.


>     - What is "Resourse base Url" configuration?
>     When I changed it for counter app for example,  static files url are not
> changer and links are not good e.g
>     /seaside/files/WAStandardFiles/toolbar.css

This setting is only used if you are sending #resourceUrl: to some
tags. WACounter doesn't use it, therefor nothing changes.

Lukas

--
Lukas Renggli
http://www.lukas-renggli.ch
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Reply | Threaded
Open this post in threaded view
|

Re: Seaside deployment help

Luc Fabresse
Tanks but...

What about a one-liner that sets the server-path for all applications?

Where is it ? How does it works ?
Changing the "server path" in the config app doesn't do the job...

 the urls of static resources like
/seaside/files/WAStandardFiles/toolbar.css will also be changed to /~luc/seaside/... ?

#Luc (lost in configs....)

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Reply | Threaded
Open this post in threaded view
|

Re: Seaside deployment help

Luc Fabresse
I achieve my will (generate all links with the form /~luc/seaside/...)  by doing:

1) Set "Server Hostname" and "Server Path" for all entryPoints that are Applications
 - Even if it is apache 2, it doesn't fully work without "Server Hostname"
 - foreach anApp : "Server Path" is set to : ('~luc/' , anApp basePath)

2) Correction of the config app that don't use the "Server Path" config to write links (Bug?)
In the code of:
WADispatcherComponent>>renderRowName: anEntryPoint named: aString on: html
use #baseUrl instead of #basePath

3) change links to files of libraries (WAStandardFiles, WADispatcherFiles)
e.g /seaside/files/WAStandardFiles/toolbar.css to /~luc/seaside/files/WAStandardFiles/toolbar.css

The quick and dirty solution:

WAFileHandler>>baseUrl
    ^ WAUrl new
        addToPath: '~luc/seaside/files';
        yourself

now it works and it was not painless...

#Luc


_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside