On 08/23/2011 08:58 AM, Ohad Levy wrote:
IMHO it should be a separate service, as we are planning to switch
to
apache/thin (there would be no katello startup script anymroe).
Yeah the plan is:
- As a dev, I'd like to migrate to apache2/thin
- change the application root url (/katello)
- As a user, I'd like to have katello super init script
- move initdb and depcheck out of katello init script
- new super init script "katello" (starts apache, thin and jobs)
- similar to pulp-server init script
In any case we should allow user possibility to deploy it on different
box. Since repo syncing and other long-running processes can be really
time/resource consuming, users could run it on a separate box.
I did not want to confuse users and start start katello-jobs from
katello service itself. Rather than creating one new script (katello,
katello-server and katello-jobs) I decided to postpone this after we
migrate to thin.
The installation documentation is up-to-date. I hope we will switch soon.
--
Later,
Lukas "lzap" Zapletal