[Seaside] What is the recommended setup to develop locally (on Mac OSX Lion) with Pharo and Seaside?

Philippe Marschall philippe.marschall at gmail.com
Sun Jan 8 20:44:56 UTC 2012

2012/1/8 Helene Bilbo <thereluctantprogrammer at fastmail.fm>:
> As long i was working without the possibility to upload files in my seaside
> application i just worked with the seaside one-click image. Now i wonder
> what is the best way to develop on a local machine when working with static
> files - when on the server where the application will run later it will run
> with apache like described in the book in chapter 22.3.
> 1) I read on the newsgroups that it is not recommended to work via RFB
> directly on the real server (where the application will run later).

That's true.

> 2) Is the best option a local installation of apache?


> How do I configure it (on Mac OSX Lion)?

See the following chapters [1] [2] in the book.

I use the following in /etc/apache2/other/seaside.conf but this
doesn't deal with files.

<Location />
	Order allow,deny
	Allow from all
	ProxyPass ajp://localhost:8003/
	ProxyPassReverse ajp://localhost:8003/

> Is it easy to migrate the application to the real server
> (where the application will run later) this way?


> 3) Is it a good option to let the Pharo/Comanche Server do the serving of
> static files while developing on the local machine?

It's generally best to have your development setup match your
production setup. Less surprises in production this way.

> How do I configure it?
> What do I have to change when i start uploading the application to the real
> (where the application will run later) server?

It's generally best if you have some sort of automated build process
that builds your production image. Then upload the image instead of
manually loading the code in the production image.

> I know this has been asked on the newsgroups many times and there were many
> answers - but for a beginner like me with no prior experience in
> (web)developing thats the biggest obstacle up to now.. A small tutorial for
> this task would be very welcome on the seaside homepage or in the book.

Our deployment story sucks (everybody has to invent his own) we're
aware of this.

 [1] http://book.seaside.st/book/advanced/deployment/deployment-apache/configure-apache
 [2] http://book.seaside.st/book/advanced/deployment/deployment-apache/serving-files


More information about the seaside mailing list