sysdweb
Control systemd services through Web or REST API
Installation
Prerequisites
If you are a Ubuntu/Debian user you need to install libsystemd-dev, for
CentOS users the package is systemd-devel.
From source
git clone https://github.com/ogarcia/sysdweb.git
virtualenv3 ./sysdweb-venv
source ./sysdweb-venv/bin/activate
cd sysdweb
pip install .
From pypi
virtualenv3 ./sysdweb-venv
source ./sysdweb-venv/bin/activate
pip install sysdweb
For Arch Linux users
Arch Linux users can install sysdweb from AUR.
Run
First take a look to sysdweb.conf file to configure sysdweb. Is self
explanatory.
You can place sysdweb.conf in /etc for system, in user home
~/.config/sysdweb/sysdweb.conf or in same directory where you run sysdweb.
Once you have configured sysdweb, simply run.
sysdweb
By default sysdweb listen in 10088 port to 127.0.0.1, you can change listen
port and address with -p and -l or via environment variables.
sysdweb -p 9080 -l 0.0.0.0
Current config environment variables are the following.
| Variable | Description |
|---|---|
SYSDWEB_CONFIG |
Config file location |
SYSDWEB_HOST |
Listen address |
SYSDWEB_PORT |
Listen port |
SYSDWEB_LOGLEVEL |
Log level, effective values are WARNING, INFO and DEBUG |
API
You can control configured services via REST API, for example, with curl.
The API endpoint is /api/v1/<service>/<action>, always GET and response
a json with following format.
{
"<action>": "<result>"
}
The <service> tag is defined in config file and match with section label.
For example, in following config, the service would be ngx.
[ngx]
title = Nginx
unit = nginx.service
The posible <actions> are.
- start
- stop
- restart
- reload
- reloadorrestart
- status
- journal
All actions (except status and journal) return as result OK if can
communicate with DBUS or Fail if any error occurs.
For status action, the posible responses are.
- active (started unit)
- reloading
- inactive (stopped unit)
- failed (stopped unit)
- activating
- deactivating
- not-found (for inexistent unit)
By default /api/v1/<service>/journal returns 100 tail lines of journal
file of <service> unit. You can specify the number of lines by this way.
/api/v1/<service>/journal/200
In the example defined above all valid endpoints are.
http://127.0.0.1:10088/api/v1/ngx/start
http://127.0.0.1:10088/api/v1/ngx/stop
http://127.0.0.1:10088/api/v1/ngx/restart
http://127.0.0.1:10088/api/v1/ngx/reload
http://127.0.0.1:10088/api/v1/ngx/reloadorrestart
http://127.0.0.1:10088/api/v1/ngx/status
http://127.0.0.1:10088/api/v1/ngx/journal
http://127.0.0.1:10088/api/v1/ngx/journal/<number>
Metadata
Release files for sysdweb 1.1.7
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| sysdweb-1.1.7.tar.gz | 316.7 kB | Details |
Release files / sysdweb-1.1.7.tar.gz
| Download URL | sysdweb-1.1.7.tar.gz |
|---|---|
| Size | 316.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d7ceccac7d0d6feb283b3d3a3c5c1a926d0c6efb2735e43410698ac62eb99bd5
|
|
BLAKE2b-256 checksum How to use checksums |
fbda5b33f6169b1f86b39d5c33887eb22e4c244db67590e49d17b07d89d6b2ee
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.10.18
|