[Seaside] How to deploy Seaside VisualWorks behing Apache

James Robertson jrobertson at cincom.com
Tue Oct 30 13:01:35 UTC 2007


There are two fairly simple ways to deploy on Apache, neither of which involves recompilation.

1) Use the Perl CGI relay, and just edit the Perl file to fit your needs

2) Use Apache Proxy Port support, and just have Apache forward requests to the VW server


  ----- Original Message ----- 
  From: Maarten MOSTERT 
  To: seaside at lists.squeakfoundation.org 
  Sent: Tuesday, October 30, 2007 8:44 AM
  Subject: Re: [Seaside] How to deploy Seaside VisualWorks behing Apache


  Hi,

   

  Thanks for the previous replies. Having said that this Seaside hosting thing really is a pain job.

   

  For the additional apache modules I seem to need to recompile my Apache distribution 2.061 setting compiler flags in the rebuild configuration file. I managed to do this rebuild and reinstall on my local Linux machine but there seems to be some subtle difference in loading these modules at runtime or including them during a rebuild. If anyone has an apache configuration file that works and which I can compare with mine then that would be very welcome.

   

  I separately continued with VW’s waveserver to try to install the cgi relay as it has this merit of being well documented.

   

  I still don’ know much from Linux so I tried the example on page 87 of the WebServerConfig.pdf which among other things states:

   

  7 Make both the directory and the file readable by the apache group.

   

  chown -R root.apache /etc/VisualWave

   

  chmod -R g+r /etc/VisualWave

   

  The last comment showed an impressive list of errors before making my remote machine inoperative without any network connection (No more Putty, FTP or whatever) and ready to reinstall the OS (I love Linux). This command most likely should have been something like: chmod +r /etc/VisualWave

   

  Rgrds,

   

  @+Maarten,





    > Boris Popov a écrit : 
      > You forgot to enable preserve host.
      > 
      > Cheers!
      > 
      > -Boris
      > (Sent from a BlackBerry)
      > 
      > ----- Original Message -----
      > From: seaside-bounces at lists.squeakfoundation.org 
      > To: maarten.mostert at wanadoo.fr ; Seaside - general discussion 
      > Sent: Thu Oct 18 01:55:55 2007
      > Subject: Re: [Seaside] How to deploy Seaside VisualWorks behing Apache
      > 
      > FWIW,
      > 
      > Over here we don't use the cgi or cgi-perl gateway but apache mod_proxy.
      > 
      > Configure your httpd.conf with:
      > 
      >         ProxyPass /yourapp/ http://ip_of_your_internal_swazoo:port/ <http://ip_of_your_internal_swazoo:port/>
      >         ProxyPassReverse /yourapp/ http://ip_of_your_internal_swazoo:port/
      > 
      > in your section. And have the mod_proxy (in apache 2.0 or 2.2 the proxy, proxy_connect and proxy_http) modules enabled.
      > 
      > HTH,
      > 
      > Wouter
      > 
      > 
      > On 10/11/07, Maarten Mostert < maarten.mostert at wanadoo.fr <mailto:maarten.mostert at wanadoo.fr> > wrote:
      > 
      >         Hi,
      >        
      >         I have a VW-seaside application which I want to run on a dedicated remote server with Fedora 5, Cpanel and Apache 1.3.
      >        
      >         I stripped my image to headless (avoiding the X console error) and this responds nicely on my localhost XP box and starts correctly on the remote server.
      >        
      >         According to the Seaside Faq: "You can run Seaside under VisualWorks behind Apache using either the the CGI gateway or the CGI Perl Interface." it furhter indicates numerous reasons why this does not work out of the box under 7.3.
      >        
      >         Is this still true under 7.5 ?.
      >        
      >         If I understood well this server subject brings me back to the Webserver config documentation on page 87 which gives a sample installation for Linux Apache stating:
      >        
      >         To install the gateway for use with Apache 1.3 running under RedHat 7.1:
      >         1 Login as root.
      >         2 Copy the Linux CGI gateway (/waveserver/waverelays/cgi/linux86/cgi2vw) to the /var/www/cgi-bin directory.
      >        
      >         As I hardly understand anything here I try to follow the documentation for as far as I can.
      >        
      >         My problem now is that I don't have a /var/www/cgi-bin directory, so where should I copy this file ?
      >        
      >         Rgrds,
      >        
      >         @+Maarten,
      >        
      >        
      > 
      >         _______________________________________________
      >         seaside mailing list
      >         seaside at lists.squeakfoundation.org <mailto:seaside at lists.squeakfoundation.org>
      >         http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside <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 --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20071030/c6a5b3b0/attachment-0001.htm


More information about the seaside mailing list