Kanedama
Kanedama uses Ghost.py to save Heroku invoices as images and will also email them to you.
Why? Because Heroku doesn’t provide any “hard copy” of your invoices, and logging in to the web UI just to screenshot them is boring.
Installation
In order for Ghost.py to work, you’ll need to install either PySide or PyQt. For me, that’s:
% sudo apt-get install python-pyside
Then you can sudo pip install kanedama.
Configuration
You need to create a config.ini file that contains your Heroku API key (see config.example.ini to get started).
By default, we check for $HOME/.config/kanedama/config.ini, so it’s best to keep your config there.
Alternatively, you can just provide the API key via the --key argument.
Automation
Stick something like this in your crontab:
01 1 25 * * your_username /usr/bin/python /usr/local/bin/kanedama.py --email=you@example.com
Metadata
Release files for Kanedama 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 |
|---|---|---|---|---|
| Kanedama-0.1.1.tar.gz | 3.9 kB | Without provenance | Details for Kanedama-0.1.1.tar.gz |
Release files / Kanedama-0.1.1.tar.gz
| Download URL | Kanedama-0.1.1.tar.gz |
|---|---|
| Size | 3.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8eb7af8391609696c414f3fd90c2c2a97908f1c078c82ce61be7c5081d92fdba
|
|
BLAKE2b-256 checksum How to use checksums |
4ab86f44e8c86a361cb4af7c91d77db1ef7efa98c6f1178b5275f29e924dc423
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for Kanedama 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.