whatsup
whatsup is an outage escalation tool for a list of sites and contacts
Installing whatsup
whatsup is installable via easy_install or python setup.py in the usual way from the python source at https://svn.openplans.org/svn/whatsup. The recommended installation procedure is with virtualenv:
python <(curl http://svn.colorstudy.com/virtualenv/trunk/virtualenv.py) whatsup cd whatsup . bin/activate mkdir src cd src svn co https://svn.openplans.org/svn/whatsup cd whatsup python setup.py develop
You will also need data files (.ini) for contacts and sites. By default these live in ${VIRTUAL_ENV}/src/whatsup/contacts and ${VIRTUAL_ENV}/src/whatsup/sites, though this is configurable.
Instantiating whatsup
whatsup is served by the paste .ini file:
paster serve whatsup.ini
Application options may be specified in this .ini file in the [app:whatsup] section prefixed with whatsup.:
contacts, sites: location of the contacts and sites files. can be a single file or a directory containing .ini files
auto_reload: whether to reload the configuration on each request
ping: whether to ping the sites
ping_frequency: how often, in seconds, to ping the sites
smtp_from: who to send email as if the user does not specified
smtp_server: mail server to use. If not specified, whatsup will not send email
whatsup contact .ini files
A contact .ini file contains one or more sections, each corresponding to a contact. The name of the section should be the name of the contact. Several data are specifiable for each contact:
email: comma separated list of email addresses.
phone: comma separated list of phone numbers
irc: comma separated list of IRC names
aim: AIM screenname
url: canonical web presence
contact: description of how to contact this person, or a filename containing that information
For each comma separated list, the first item is considered primary.
whatsup site .ini files
A site .ini file contains one or more sections, each corresponding to a website. By convention, the section name is the domain name of the site. Several data are specifiable for each site:
url: location of the site. If not specified, the url will be from the section name (presumedly the domain name)
contact: comma separated list of contacts in case of site outage
description: brief description of the website
outage_procedure: if specified, a description of what to do in case the site is down or a filename containing that information. By default, this links to the contact form which emails the contacts upon submission.
trac: URL of the associated Trac site
Metadata
Release files for whatsup 0.1.1
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 |
|---|---|---|---|---|
| whatsup-0.1.1.tar.gz | 47.0 kB | Without provenance | Details for whatsup-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| whatsup-0.1.1-py2.5.egg | Legacy Egg format | - | - | Details for whatsup-0.1.1-py2.5.egg |
Total release size: 102.6 kB
Release files / whatsup-0.1.1.tar.gz
| Download URL | whatsup-0.1.1.tar.gz |
|---|---|
| Size | 47.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cdfe90ee0d0d011fef341ec6755742b2a7ec95f9dc283ce40f80f29c5b40c55b
|
|
BLAKE2b-256 checksum How to use checksums |
9ea3e00c52310ad2534921dd83e8a6218c6ede43666ce30c118af9b1b31521f0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / whatsup-0.1.1-py2.5.egg
| Download URL | whatsup-0.1.1-py2.5.egg |
|---|---|
| Size | 55.5 kB |
| Tags | Egg |
|
SHA-256 checksum How to use checksums |
ad62ed745a0bd86dfbb019e1d2f73c87b46269be064e0b5dd17287dac0abd4ae
|
|
BLAKE2b-256 checksum How to use checksums |
c279b506c33c9ad52a9d1a8981303d8ad07aad29ee89791a4bc78580726533ef
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for whatsup 0.1.1
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.