WASD updated
It took some preparation because quite a lot of basic config of the server (not the sites) has changed and so the process needed some time: Another naming convention and location of logicals, and a change in configuration-schema made this update less straight forward than normally is the case. Including full startup (and shutdown) of the web server – and surrounding software: like the PHP engine and mail support.
Not forgetting the daily, weekly and monthly processing – it all needed to be overhauled.
To be sure I could reverse, if needed, the whole installation was to be performed on a new directory tree, fully separated – as far as the server environment was involved – from the old version.
Most preparation could be done before the server was updated, but it could only be checked after the new version was installed. That process itself required the running (9.3) server to be shut down. So I did, and it will have caused some timeout when the content was accessed.
I could have done simpler, perhaps – since there is a CLONE option, but that did not exist in pre-v10 versions. i think.
The update itself was flawless, as could be expected. Restarting the server itself was neither – but since the installation did copy sample configuration into the environment, I couldn’t get to the site itself. I had to remove these files ($ delete WASD*.CONf;0), then stop and restart the server before I could access the sites. Onl;y a few tweaks were required in the configuration (things did change….), and I could start the site used for system management: handy, because that also faciliates the server admin pages – including the WATCH facility. But other sites – including the normal site, were not, and the WATCH output immediately showed why: I still had to copy a number of files from the previous environment; including some executables and files that reside within the server environment.
Now, within an hour, at least most of the most important features seem to work. Just mail access doesn’t work, but that will be solved soon…
Update
The last hurdles have been taken…I had made a minor adjustment to the SoyMail configuration file, and that causes a double-quote to get lost. That’s why the footer didn’t show – and I couldn’t display the messages…Problem solved.
Other minor issues were easily solved by copying some files from the old to new environment. It’s just the Java-based terminal emulator that doesn;t work – but that is useless anyway so I can get rid of it. There is an alternative I can use with this version of WASD – and latest Chrome browser (and next versions of Firefox and IE), based on websockets…. So next action is to build this HTTP-based terminal emulator
Update 2
Done, and included in the system management site – which is (as can be expected) protected. It does work – running Chrome since that’s currently the only browser on my system that supports WebSockets – but connecting to the site will fail on authentication. Checked that with Mark Daniel who provided the code: it’s not fit -yet – to be run in an authenticated environment.
So now I have to find a way to make that path free from authentication and still make the access impossible ig you’re not authenticated. Can be done, but requires good thinking….