Hi,
In using Magma in the mixed client/server mode, I found that image startup/shutdown time became a bit of a nuisance - Magma takes its time to reconnect and disconnect. So I decided to move to a separate server, one on my laptop for all my little projects.
Most of my work (not much, being very busy with some network debugging around Kolibri) these days revolves around Kilauea, which wants to provide an easy out-of-the-box experience around Magma+Seaside, so I decided to make this thing user-friendly by adding a simple management console in HV. As an added advantage, this enables me to run the image as an NT service...
http://de-1.tric.nl/~cg/mc/Kilauea-Magma%20Server%20Management-CdG.1.mcz
has the code, but even better:
http://de-1.tric.nl/~cg/MagmaServer-CdG.1.zip
has the ready-to-run image (the image says to start a service on port 21000, but as you have it with beta software, I didn't do a shutdown before shipping the thing so it'll run out-of-the-box on this port). In other words, under Linux:
% mkdir MagmaServer % cd MagmaServer % unzip /tmp/MagmaServer-CdG.1.zip % nohup squeak -headless magmaserver.image &
and you should be able to connect to http://localhost:21000/ a few seconds later. On Windows:
- Unpack the zip file in where you want the server to run; - Copy Squeak.exe to that directory and create a Squeak.ini there that has: [Global] ImageFile="C:<full path to dir>\magmaserver.image" - Open a windows console window on the directory and do: Squeak -service: "Magma Server" - Follow the prompts, but don't start the service yet. Go to the service console (Start->Run services.msc), open the properties on the Magma Server service, and in the second tab switch it to run under your account - for some reason, running Squeak under the system account as a service never works. - Apply settings and start the service. - Surf to http://localhost:21000/
MacOS X, Risc OS, ...: - Send me a machine and I'll figure it out ;-)
This is not a top-priority project for me, but if you have comments and patches, i'll do my best to shove out another version in a week or two if any big issues pop up.
Happy hacking!
Cees
Forgot this one:
ObScreenshot: http://www.cdegroot.com/blog/wp-content/uploads/thumb-kilaueamagmaservermana...
:)
Sorry that was the thumbnail. Here's the full version: http://www.cdegroot.com/blog/wp-content/uploads/kilaueamagmaservermanagerscr...
I need to go to bed, I think.
It does not work for me.
When creating a new database and clicking on 'stats' or 'shutdown' I get 'Not a running Magma instance'. When I try to it using another image I get the exception 'MaNetworkError: Cannot connect to 192.168.1.10:21001'.
Lukas
-- Lukas Renggli http://www.lukas-renggli.ch
[please remove squeak-dev on reply, taking this to the magma list]
On 12/8/05, Lukas Renggli renggli@gmail.com wrote:
When creating a new database and clicking on 'stats' or 'shutdown' I get 'Not a running Magma instance'. When I try to it using another image I get the exception 'MaNetworkError: Cannot connect to 192.168.1.10:21001'.
Both seem to indicate that the create database didn't work. No walkbacks if you run the image headful and try to create a db? Has the directory been created?
Both seem to indicate that the create database didn't work. No walkbacks if you run the image headful and try to create a db?
Yep, no walkbacks in the headful image.
Has the directory been created?
Yes, there is a directory with the files:
applied.images commitPackages objects objects.idx
-- Lukas Renggli http://www.lukas-renggli.ch
-- Lukas Renggli http://www.lukas-renggli.ch
Well, then I fear you'll have to do some debugging :P. The code is simple: create the database, start a listener. The listener bit is missing in your image - could it be that between my snapshot and your startup, some network code didn't pick up changes?
I'm just speculating - only tested the image on one box, so any help here would be tremendously useful.
On 12/8/05, Lukas Renggli renggli@gmail.com wrote:
Both seem to indicate that the create database didn't work. No walkbacks if you run the image headful and try to create a db?
Yep, no walkbacks in the headful image.
Has the directory been created?
Yes, there is a directory with the files:
applied.images commitPackages objects objects.idx
-- Lukas Renggli http://www.lukas-renggli.ch
-- Lukas Renggli http://www.lukas-renggli.ch
Well, then I fear you'll have to do some debugging :P. The code is simple: create the database, start a listener. The listener bit is missing in your image - could it be that between my snapshot and your startup, some network code didn't pick up changes?
It does work from a workspace. As far as I understand KmsManager it doesn't properly encode/parse the database-names, sometimes fileName is empty, sometimes it is the full-path, sometimes only the file-name, ...
Lukas
-- Lukas Renggli http://www.lukas-renggli.ch
On 12/9/05, Lukas Renggli renggli@gmail.com wrote:
It does work from a workspace. As far as I understand KmsManager it doesn't properly encode/parse the database-names, sometimes fileName is empty, sometimes it is the full-path, sometimes only the file-name, ...
What platform are you using? I had to do some full-path/local name conversions, could very well be that something goes wrong there (although as far as I know I used platform-independent methods only - I tested this on Windows)
What platform are you using? I had to do some full-path/local name conversions, could very well be that something goes wrong there (although as far as I know I used platform-independent methods only - I tested this on Windows)
I am using the unix vm on linux and os x.
Maybe it helps just to encode #localName into the urls and build the full path from there using FileDirectory default fullNameFor: param? I noticed some URLs that look like "/shutdown//services/foobar".
-- Lukas Renggli http://www.lukas-renggli.ch
squeak-dev@lists.squeakfoundation.org
-
Cees De Groot -
Lukas Renggli