papavisor
A control script for supervisor’s - the Papa (german Dad) of supervisors.
With papavisor you can:
Get the status of all supervisors one a machine (you can configure remote supervisor though).
Start/stop/restart grouped supervisor programs with priorities and startsecs in between.
Talk to multiple supervisors in parallel (by using asyncio).
apapavisor finds supervisord.cfg files himself - no need to configure each instance.
Requirements
Unix like System
Python >3.4.0
Install
papavisor is available over pypi:
$ pip3 install papavisor
Configuration
On the first start papavisor copies config files to ~/.config/papavisor/ if theres no /etc/papavisor directory. Papavisor reads all .json files sorted and merges them into one big configuration OrderedDict.
papavisor files:
00_default.json - Contains the defaults for each project, they will get copied and then overwritten by the per project values.
01_template.json - An template for “manual” project witch overwrites the defaults above.
apapavisor - The Auto papavisor reads apapavisor.sh only.
Usage
When you install this package you get two excecutables:
papavisor - The supervisord control script.
apapavisor - A wrapper witch searches for supervisord.conf files and passes them to papavisor, its the Auto papavisor as you need nearly no configuration for that.
General usage:
$ (a)papavisor [project-or-all] [action] [group-or-program]
The default is:
$ (a)papavisor all status all
For example, to restart all zope instances:
$ apapavisor all restart zopes
To restart all python stuff on project ploneconf:
$ apapavisor plonec restart python
All actions:
$ apapvaisor <project-or-all> status <group-or-program> $ apapavisor <project-or-all> start <group-or-program> $ apapavisor <project-or-all> stop <group-or-program> $ apapavisor <project-or-all> restart <group>
License
papavisor is licensed under the MIT license.
Contribute
Issue Tracker: https://github.com/webmeisterei/papavisor/issues
Source Code: https://github.com/webmeisterei/papavisor
Support
If you are having issues, please let us know.
Changelog
0.1.0 (2016-02-14)
Also wait on TCP Check if startsecs have been given. [pcdummy]
Add TCP Check and start_extra. [pcdummy]
Reverse the priority on start. [pcdummy]
0.0.1a3 (2016-02-11)
Fix apapvisor config path detection. [pcdummy]
0.0.1a2 (2016-02-10)
Fix package installation, move config to ~/.config. [pcdummy]
Add texttable for the status output and psutil for memory info. [pcdummy]
Link pypi, cleanup main(). [pcdummy]
Use argparser and smaller bugfixes. [pcdummy]
Use sys.prefix for config files. [pcdummy]
Added support for connecting to ‘unix://’ sockets. [pcdummy]
Add an option ‘enable’ to disable projects. [pcdummy]
README.rst, papavisor is available over pip. [pcdummy]
Fix “python3 setup.py develop”. [pcdummy]
0.0.1a (2016-02-10)
papavisor was born. [pcdummy]
Metadata
Release files for papavisor 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| papavisor-0.1.0.tar.gz | 11.6 kB | Without provenance | Details for papavisor-0.1.0.tar.gz |
Release files / papavisor-0.1.0.tar.gz
| Download URL | papavisor-0.1.0.tar.gz |
|---|---|
| Size | 11.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9c344c85d28fbb8eee3568040492fa85a250e4146ab603b6662ccb935ac6aa9d
|
|
BLAKE2b-256 checksum How to use checksums |
861433522ad49f6b14157d0933b69b8bb0c30b0fe4d11b1308a8eddd3a1d2239
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for papavisor 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.