summaryrefslogtreecommitdiff
path: root/src/leap/bitmask/backend_app.py
AgeCommit message (Collapse)Author
2015-10-07[bug] pass on standalone flag to commonIvan Alejandro
- Related: #7512
2015-10-06[bug] store logs in the right placeIvan Alejandro
Load flags before creating logger so the logs path considers the standalone flag. Move the log file path definition to the function, otherwise it will calculated during import and (most likely) before defining the flags.STANDALONE value. Create logger inside `run_frontend` right after knowing if we are standalone or not. - Resolves: #7512
2015-10-06[bug] store zmq certs in the right pathIvan Alejandro
Change KEYS_DIR for a function, so the path does not get defined on import (and most likely) before the flags are defined. Move the flags_dict call before the generate_zmq_certificates call. Otherwise the standalone flag won't be set properly. - Resolves: #7512
2015-08-07[doc] clarify that backend lives in a subprocessKali Kaneko
2015-08-05[feat] Move the updater code from the launcherRuben Pollan
The new pyinstaller method will rule out the launcher, we need the updater working inside bitmask client. - Closes: #7291
2015-07-20[bug] start the events server when reactor is runningKali Kaneko
otherwise, events are not correctly registered - Resolves: #7149
2015-06-22[feat] handle twisted/logging logs with logbookIvan Alejandro
Forward Twisted logs to logging and use logbook to handle logging logs. Store the bitmask logs on the config folder.
2015-06-22[feat] replace old log handler with new oneIvan Alejandro
Replace logging.getLogger with custom get_logger. Remove some unneeded dependencies and reorder other.
2015-06-10[bug] don't run event server on the standaloneIvan Alejandro
We don't need to run the event server on the backend if we are running from the standalone bundle since the launcher takes care of that. - Related: #7126
2015-05-29[bug] move events server init to backenddrebs
If the events server is initialized in a different process than the backend, the txzmq socket raises an "zmq.error.ZMQError: Interrupted system call" exception during the events server initialization. Despite that, communication seems to work flawlessly after the initialization. Moving the events server initialization to the same process as the backend causes the exception to not be raised during events server intialization.
2015-02-20Fall back to plain ZMQ if Curve is not available.Ivan Alejandro
Use global flag for ZMQ_HAS_CURVE. Closes #6646
2014-12-29Create the certificates if they don't exist.Ivan Alejandro
Fix typo for signal disconnection. The backend is the one who always creates the certificates. Either if it is run separately or in a process in the same app as the frontend.
2014-12-19Allow frontend and backend to be run separately.Ivan Alejandro
Add the 'check_online' method to check whether the backend is accessible or not. Reduce the wait for running threads timeout on quit. Add retry feature to the backend requests send.
2014-07-24Add frontend alive check to the backend.Ivan Alejandro
Stop the backend if the frontend process does not exist any more and backend is not a daemon.
2014-07-14Add file docstrings.Ivan Alejandro
2014-07-14Handle SIGINT/SIGTERM in processes.Ivan Alejandro
2014-07-14Send the flag module values to the processes.Ivan Alejandro
Add serialize/deserialize to dict helper.
2014-07-14Move the backend starter to its own file.Ivan Alejandro
2014-06-05Reorder logging helpers and handlers.Ivan Alejandro