Introduction
Most systems have some form of notification systems. This library tries to use them to tell the user that his zope is up and running. This can be useful in development, when one needs to restart often, and does not want to watch the system starting up.
Supported operating systems
[x] Linux (via notify-send)
[x] Mac (via growlnotify or terminal-notifier)
[ ] Windows
Linux
If your linux flavor does not provide notify-send nothing really happens.
Mac OS
For MacOS 10.8 you might want to use the notification system via terminal-notifier since Growl is no longer free.
For MacOS 10.x-10.7 you need Growl notification system and growlnotify extra script. Otherwise, nothing will happen. See official instructions for installing growlnotify script.
Installation
Add the package name ot the eggs part of your zope2 instance and rerun buildout.
Changelog
0.6.4 (2012-08-02)
Add support for notification centre in MacOS 10.8 via https://github.com/alloy/terminal-notifier/downloads [pbauer]
0.6.3 (2012-08-02)
another attempt at building a working egg. [pbauer]
0.6.2 (2012-06-26)
fixed Manifest.in even more [do3cc]
0.6.1 (2012-06-26)
fixed Manifest.in [do3cc]
0.6.0 (2012-06-26)
Added Mac Support with growl [Laurent Lasudry]
0.5.2 (2012-01-04)
fixed wrong setup_requires statement [do3cc]
0.5.1 (2012-01-04)
Brown paper bag release. Thanks to Mark van Lent for the fixes [markvh, do3cc]
0.5 (2012-01-03)
Package created using zopeskel [do3cc]
Metadata
Release files for collective.backtowork 0.6.4
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 |
|---|---|---|---|---|
| collective.backtowork-0.6.4.zip | 10.1 kB | Without provenance | Details for collective.backtowork-0.6.4.zip |
Release files / collective.backtowork-0.6.4.zip
| Download URL | collective.backtowork-0.6.4.zip |
|---|---|
| Size | 10.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
28a595d2dbade6c9b6d1a7d43fa7665338bbd9cfda8c37de17b50830b86a49d2
|
|
BLAKE2b-256 checksum How to use checksums |
0076df2c4555537e2b7249fef8e87b80ab706e89b7270de628454761d51b5c61
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for collective.backtowork 0.6.4
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.