Webware for Python

On 18 Apr 2004, rd said:

> I have been running Webware 0.7.0 for longer than I can remember. 
> What this means is that I also can't remember all of the setup steps
> that were required.
> 
> It is time for me to upgrade to 0.8.1 and I am afraid of breaking my
> Webware server while doing this.
> 
> Would someone be kind enough to remind me of those files / configs
> that I have to backup before the upgrade.  I do not want to lose my
> setup / config.  Additionally, a quick review of the proper way to
> upgrade would be helpful.

Heh. Obviously you haven't touched it in a while. Read the
Install(ation) section of Jason's Webware tutorial. 

http://www.opensky.ca/~jdhildeb/webware/

Or the 0.8.1 install guide:

http://www.webwareforpython.org/Webware-0.8.1/WebKit/Docs/InstallGuide.ht
ml 

I don't know if going from 0.7.0 to 0.8.1 will break anything, but it
doesn't really matter because it's easy to setup two webwares on the
same machine -- webware lives entirely out of the directory you untar it
to. So, just untar 0.8.1 somewhere that's NOT over top of 0.7.0, then
run the install script (which doesn't install any files to your python
path -- it only updates things in that webware directory). Now, make a
new appserver (run "python bin/MakeAppWorkDir.py
/where/you/want/the/appserver"), then synchronize the settings of the
config files in the new appserver/Config directory with the old one, and
you should be good to go. 

The Apache mod_webkit might've changed from 0.7 to 0.8, so you might
have to upgrade that to be able to try out your new config. 

Purdy easy, if you know what/why you're doing.

Chris Gahan wrote:
> On 18 Apr 2004, rd said:
>>I have been running Webware 0.7.0 for longer than I can remember. 
>>What this means is that I also can't remember all of the setup steps
>>that were required.
>>
>>It is time for me to upgrade to 0.8.1 and I am afraid of breaking my
>>Webware server while doing this.
>>
>>Would someone be kind enough to remind me of those files / configs
>>that I have to backup before the upgrade.  I do not want to lose my
>>setup / config.  Additionally, a quick review of the proper way to
>>upgrade would be helpful.
> 
> 
> Heh. Obviously you haven't touched it in a while. Read the
> Install(ation) section of Jason's Webware tutorial. 
> 
> http://www.opensky.ca/~jdhildeb/webware/
> 
> Or the 0.8.1 install guide:
> 
> http://www.webwareforpython.org/Webware-0.8.1/WebKit/Docs/InstallGuide.ht
> ml 
> 
> I don't know if going from 0.7.0 to 0.8.1 will break anything, but it
> doesn't really matter because it's easy to setup two webwares on the
> same machine -- webware lives entirely out of the directory you untar it
> to. So, just untar 0.8.1 somewhere that's NOT over top of 0.7.0, then
> run the install script (which doesn't install any files to your python
> path -- it only updates things in that webware directory). Now, make a
> new appserver (run "python bin/MakeAppWorkDir.py
> /where/you/want/the/appserver"), then synchronize the settings of the
> config files in the new appserver/Config directory with the old one, and
> you should be good to go. 
> 
> The Apache mod_webkit might've changed from 0.7 to 0.8, so you might
> have to upgrade that to be able to try out your new config. 

There may have been a couple changes to mod_webkit (I can't remember), 
but none to the protocol, so an old mod_webkit can talk to a newer 
AppServer and vice versa.

Chris should also look at MakeAppWorkDir.py if he isn't using that 
already -- it will set up a kind of minimal directory of 
application-specific stuff.  He can copy over those files from his 
application's files, and then in the future code will be separate from 
the stock Webware distribution.

   Ian

On 19 Apr 2004, Ian Bicking said:

> There may have been a couple changes to mod_webkit (I can't remember),
> but none to the protocol, so an old mod_webkit can talk to a newer 
> AppServer and vice versa.
> 
> Chris should also look at MakeAppWorkDir.py if he isn't using that 
> already -- it will set up a kind of minimal directory of 
> application-specific stuff.  He can copy over those files from his 
> application's files, and then in the future code will be separate from
> the stock Webware distribution.

What an odd reply.. :)

It's good to know that mod_webkit's protocol hasn't changed. That's handy. 
rdg is the one who's having the upgrade problems though. ;)