After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 617653 - Plone instance needs a way to auto-start on boot
Plone instance needs a way to auto-start on boot
Status: RESOLVED FIXED
Product: sysadmin
Classification: Infrastructure
Component: Other
unspecified
Other Linux
: Normal normal
: ---
Assigned To: GNOME Sysadmins
GNOME Sysadmins
Depends on:
Blocks:
 
 
Reported: 2010-05-04 13:48 UTC by Jeff Schroeder
Modified: 2011-01-03 21:37 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Jeff Schroeder 2010-05-04 13:48:01 UTC 
With some coffee and a little bit of poking around, I figured out how to start up the zope instance on socket for website-editors.gnome.org.

It involves:
su - wgoplone
cd development/editors/bin/
./instance start
./run-deliverance &

# Make sure things look good
lsof -i tcp:5001
wget -S -q -O /dev/null http://website-editors.gnome.org

However, this should start on boot. Someone with an understanding of zope further than myself should write an init script.
Comment 1 Christer Edwards 2010-12-28 20:23:56 UTC 
I've put in place a rudimentary start script that seems to work. The stop functionality is still broken, but this might be enough for boot-time support.

I'll give it another look tomorrow and see if I can clean it up some more.
Comment 2 Christer Edwards 2011-01-03 21:37:06 UTC 
I've improved (if you can call it that) the shutdown script. It does what it needs to do, but it does feel like a bit of a hack.

In any case, /etc/init.d/plone {start|stop|restart} are functional on socket, and it is set to autostart at boot.

My understanding is we're likely not going to stick with plone but move to WP instead, so I'm not going to worry too much more about perfecting this script.