Plug
Plug is a tool to automate packaging and installation of Python daemons including Python dependencies in the package. It grew out of my use of Supervisor and the problems of managing large numbers of processe.
Installing
Use pip!
pip install plug
Creating a Plug
To create a plug you create a config file with minimal information then run
plug create {package_name}
The config file looks something like:
[server1] command=bin/python -m SimpleHTTPServer 8001 user=plug_user
You will be left with a plug:
{package_name}.server1.plug
Installing a Plug
Once you put this on your system you can run
plug install {package_name}.server1.plug
This will create a new virtualenv in /srv/plug ready to be setup as a daemon. To have runit start the process you run:
plug setup {package_name}.server1.plug
Optionally with the argument –number to setup multiple daemons from that package. The number causes multiple links to be created in /etc/sv and /etc/srv.
Uninstalling a Plug
To uninstall the plug use the uninstall command
plug uninstall {package_name}.server1.plug
This will also remove the links for runit.
Other Commands
Other commands included are list and status which will list all plugs installed and the runit status of each daemon instance.
Metadata
Release files for plug 0.1.3
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 | |
|---|---|---|---|---|
| plug-0.1.3.tar.gz | 9.9 kB | Without provenance | Details |
Release files / plug-0.1.3.tar.gz
| Download URL | plug-0.1.3.tar.gz |
|---|---|
| Size | 9.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1b57fc7e3cb4f4492691f7d53f01cc1f4cf973ddc1e08470212862ab01eea127
|
|
BLAKE2b-256 checksum How to use checksums |
ec69c92a924ba5dd5068ba1d10101fa0456daafe611de6bb940fd5e883f4ec77
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for plug 0.1.3
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.