From: Oliver Bock <oliver@g7...> - 2006-08-24 22:24:42
Whenever a new release of Webware comes along I:
- Create a new webwarework directory.
- Diff between the new config files and my old ones, manually copying my
- Create a symbolic link to the directory containing my servlets.
The docs appear to be silent on the matter, is this the way I'm supposed
to do it?
P.S. The Wiki is throwing a red screen of death, the stack trace of
which shows infinite recursion in UserDict.py:170.
From: Christoph Zwerschke <cito@on...> - 2006-08-25 09:43:47
Oliver Bock wrote:
> Whenever a new release of Webware comes along I:
> - Create a new webwarework directory.
> - Diff between the new config files and my old ones, manually copying my
> configuration changes.
> - Create a symbolic link to the directory containing my servlets.
> The docs appear to be silent on the matter, is this the way I'm supposed
> to do it?
This should be only necessary when the major or minor version changes,
i.e. not for updating from 0.9.1 to 0.9.2.
Between 0.8.1 and 0.9, the start scripts were changed so that workdirs
are relocatable and improved. So you had to replace the launch scripts:
AppServer (start script), webkit (rc start script for your platform),
Launch.py (a stub), AppServerService.py (a stub, on Win only).
The current release has only minor changes to rc start scripts for some
Changes in the config files are usually downward compatible. If there
are new settings, they always have a default, so they do not need to
appear in the config file. Some are not even included in the standard
config file because they are too special.
You're right, there should be a note about updating in the release
notes. Maybe there should be also a switch --update to MakeAppWorkDir.
E.g. MakeAppWorkDir would safe backups of the standard config files as
*.config.default which could be checked for changes when running with
--update, and you are given hints which settings were changed or added.
Get latest updates about Open Source Projects, Conferences and News.