Hint: Setting up Apache proxy for your Seaside host
If you’re about to deploy a new shiny application you developed with Seaside, you’re probably wondering how to go about it. Well, here’s one way of doing it and its generic enough that it may just work or require very little tweaking if you already have Apache2 installed.
Scenario:
- 1 machine with Seaside application running on a built-in web server (TinyHTTP/WebToolkit or Swazoo)
- IP: 192.168.0.2
- Port: 8008
- Path: /seaside/go/online
- 1 machine with Apache2 externally available as www.mydomain.com
- IP: 192.168.0.1
- Ports: 80 and 443
Requirements:
- All communications with the server must be encrypted via SSL
- Users attempting to connect via non-secure HTTP must be redirected to secure HTTPS
- Application must be available at www.mydomain.com/online
- Users must be redirected to /online without having to type it in every time
In a nutshell, you must have a working knowledge of Apache2, the sample config includes 2 virtual hosts and hopefully speak for itself (with a help of an odd comment here and there), the rest of Apache2 configuration is out of the scope of this article. Grab it now and take a look yourself, I’ve given up on WordPress formatting it properly for display…
Hello I don’t know where to ask. )) I want to display image file png with seaside.
I start visualworks from directory where image located. And here is images/logo.png file. I tried to show it using
renderContentOn: html
html image: ‘images/logo.png’.
I use seaside with webtoolkit/visualworks.
Dear Boris,
in your sample I see someIp:8008/online as the server of a seaside app. There is no /seaside/ in there. How do you get rid of it?
thanks,
Sebsatian
Sebastian, good question, see Michel Bany’s SeasideShortPath parcel that’s included in contributed\seaside\bonuspack.
Vladimir, see Michel Bany’s SeasideWebDesignerTool parcel from contributed\seaside\bonuspack.
P.S. Michel Bany has parcels for everything :)