Make possible to run frontend and backend as a separated apps.
Right now (finishing #5734 (closed)) we use multiprocessing to run the frontend and the backend in different process. We want to be able to run the backend as a daemon on the system start and then plug the UI.
We need to:
- handle SIGINT/SIGTERM differently
- manage curve credentials to use existing ones if the backend is running.
from #5734 (closed):
chiiph said: So after discussing this with ivan a bit, here's what it came out: - There will be an app.py to run the backend headless. - The whole-client-app.py will look for the curvemq key file (owned by the user) in a specific file in the config directory, if that exists and the backend port is open, it'll attach to the backend using that key. If the backend port is not open, then it'll launch the backend and connect to it using the key. If the key doesn't exist, it'll be generated. For the really near future: - If the backend is not running, but the key exists, it'll be regenerated before launching the backend.
(from redmine: created on 2014-07-04, closed on 2014-12-29, relates #5734 (closed), relates #4675 (closed), relates #6372 (closed))