> I also copied and updated the /usr/local/gump/README from Moof. I've updated it to comment out what has not been done (i.e. step #12).
Since 'hostname' returns brutus not brutus.apache.org (more like moof does) I've edited the README to say the workspace file is brutus.xml. > I have not yet proceeded to step 8 which involves forrest. If the > consensus is that we want to replace this with a Python solution, I can > invest the time to make that happen. I've checked-out forrest (/usr/local/gump/xml-forrest) and copied the install into (for want of a better place) /usr/local/gump/forrest. I've created a local-env-py-brutus.sh, that sets FORREST_HOME and adds FORREST to the path. We really need somebody to place these local information into a .bashrc or .profile (or wherever) so FORREST_HOME is picked up by a python script. However, I'm not that guy -- I am too out of touch with such things. BTW: Don't take this as me being intransigent and not open to moving away from forrest, this is just for here and now. I personally think we need to make forrest work for us (I want SVGs) but I think we can remove it as a mandatory requirement for HTML sites. Since I've not had much fun running gumpy.py in background (when I hang up, it dies) -- and because I need the forrest env variables I am adding this crontab entry: 0 0 * * * cd /usr/local/gump/public/gump; /bin/bash gumpy.sh Not the one I'd prefer: 0 0 * * * cd /usr/local/gump/public/gump; /usr/bin/python gumpy.py I've kicked off a Gump run on brutus. Next steps (assuming this above all works) ought be to modify HTTPD configuration to point to the results in /usr/local/gump/public/results. Anybody game to take these on? regards Adam --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
