Please do not reply directly to this email. All additional comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=693425
--- Comment #9 from Panos Christeas xrg@hellug.gr 2011-04-08 07:25:46 EDT ---
Basically, what I miss is a INSTALL (INSTALL.fedora?) file. I envision a simple doc, something like
INSTALL ON A SINGLE HOST ... Create a openerp database user: # /etc/init.d/openerp-server db-add-user Make a basic test # /etc/init.d/openerp-server db-test Install certificate. If you already have a server certificate: # /etc/init.d/openerp-server certificate-install /path/to/certificate If you don't have a certificate, openerp can create a self-signed one for you: # /etc/init.d/openerp-server certificate-create Start openerp-server: # service openerp-server start ... (snip)
Certainly interesting.
The purpose of the -serverinit subpackage was this (it is an old concept): Suppose we want to provision a system (or image ;) ) with a default, ready to work, installation of OpenERP. This cannot involve any manual configuration steps by root/postgres/openerp user. It must just start, boot, and end up with an openerp client, from which the "admin" user will be able to create his first database. I appreciate that assumptions are not welcome in RPM packaging. That's why I have isolated these steps into the 'serverinit' package.
So, at the end, you will have either a set of "post-install" steps (that will let you chose the db server, certificate etc), or an automated meta-package.
In the meanwhile, I agree to move as much as possible inside the initscript (I didn't know that extra steps apart from start/stop/status were welcome in Fedora).