Simple runit web management tool with internationalization support.
Server will run by runit-man script. Take a note that runit-man must have privileges like runsvdir process ones.
We provide runit-man cookbook to automate setup of runit-man using Opscode Chef.
Usually You should install both runit-man and thin gems to run this tool fine.
gem install runit-man thinPragmatic approach is to setup runit-man as runit service like this:
runit-man -p 14500 -rThis command installs runit-man as runit service (using default folders /etc/sv/ and /etc/service/).
Look at {file:INSTALL.md} for details.
Take a note that runit-man gem also provides config.ru rackup configuration file.
It's useful for running under unicorn/rainbows etc. runit-man --rackup=command option does cd config.ru directory && set environment && exec command.
This tool can provide additional information or actions through it's Web page.
For each known runit service this tool looks for ./runit-man/files-to-view/ folder.
Every symlink there will be shown as link to view target file content.
For each known runit service this tool looks for ./runit-man/urls-to-view/ folder.
Every file ended with .url will be shown as link to view target location (location should be written as content of this file).
For each known runit service this tool looks for ./runit-man/files-to-watch/ folder.
Symlink targets there will be tested for its mtime to be less than service start time.
Service will be indicated as dangerous (as red color) to restart if any watched file is modified since service startup.
For each known runit service this tool looks for ./runit-man/allowed-signals/ folder.
Each one-letter-named file declares that signal button should be shown in Web UI.
Signal letters listed below in REST API section.
You can read current state of services in JSON format using
GET /services.json
You can manage your services using
POST /<service name>/<command>
Supported commands: up, down, restart, switch_up (activates service), switch_down (deactivates service).
You can also send any signal to service using
POST /<service name>/signal/<signal>
Supported signals and their's meaning:
| Signal | Meaning |
|---|---|
| t | TERM |
| k | KILL |
| i | INT |
| 1 | USR1 |
| 2 | USR2 |
| a | ALARM |
| q | QUIT |
| x | EXIT |
| p | PAUSE |
| c | CONT |
| h | HUP |
| o | ONCE |
You can read tail of service log using
GET /<service name>/log/<count of tailing lines>.txt
Note that to use this feature You must do logging using
exec svlogd <options> $LOG_DIRECTORY_LOCATIONUse logger like:
exec logger -i -t "runit-man" -p local1.infoand use option -l "logger:/var/log/" where base logs directory shown after period.
Localization can be done by editing of ./i18n/*.yml locale files.
Contributions are welcome.
Runit-man provides a useful Vagrant file. To have a complete development environment:
- Grab Vagrant and Oracle VirtualBox.
- Checkout submodules:
git submodule update --init. - Setup Vagrant box:
vagrant up.
Now you have an Ubuntu 12.04 system with runit and runit-man running inside your Vagrant box