Avendesora Export — Exports Selected Accounts to a Remote Host
Avendesora Export creates Avendesora account files on remote machines that contain selected accounts. This allows you to use Avendesora on satellite hosts without maintaining two independent databases of account information. Simply install Avendesora on both your primary and satellite machines. Keep all, or at least most, of your accounts on your primary machine and configure Avendesora Export to manage the satellites. It needs to know the hostname, the path to the accounts file, the encryption keys, and the accounts you wish to export to each satellite.
For example, imagine owning a laptop, which is your primary machine, a media machine for watching videos and listening to music, and a server that contains your Bitcoin node. Assuming Avendesora is already installed on your laptop and contains all of your accounts, install Avendesora Export on your laptop and add the following file to ~/.config/avendesora-export/config.nt:
keys:
personal: F2B442F8F08A750A
work: 18A1A1A802012366
destinations:
media:
dest: media:.config/avendesora/imported.gpg
keys: personal
accounts:
- Netflix
- YouTubeTV
- Hulu
- HBO
- Disney
- Spotify
server:
dest: server:.config/avendesora/imported.gpg
keys: personal work
accounts:
- BitcoinRPC
Then, running:
avendesora-export media
exports the selected accounts to your media machine. It can be run from any directory on your laptop.
Be aware that an export simply overwrites the previously exported accounts file. You should not manually add accounts to a exported accounts file. If you would like accounts that are only local to the satellite host, simply add them to its accounts.gpg file. When you first export a file to a host, you need to add the name of that file to the accounts_files list in ~/.config/avendesora/accounts_files.
You should also be aware that the exported secrets are frozen, meaning that any generated secrets that are exported are converted to remembered secrets on the satellite.
Releases
- Latest Development Version
- Version: 0.2Released: 2026-06-28
Metadata
Release files for avendesora-export 0.2
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 |
|---|---|---|---|---|
| avendesora_export-0.2.tar.gz | 15.2 kB | Without provenance | Details for avendesora_export-0.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| avendesora_export-0.2-py3-none-any.whl | Python 3 | none | any | Details for avendesora_export-0.2-py3-none-any.whl |
Total release size: 30.4 kB
Release files / avendesora_export-0.2.tar.gz
| Download URL | avendesora_export-0.2.tar.gz |
|---|---|
| Size | 15.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e295ad3b4bbb4b95cc02c9c488d5bc02fec02424fd89126b745d8dc3479846a4
|
|
BLAKE2b-256 checksum How to use checksums |
b2f16eada5df8e99200b203160217aa388658ecc2705698e3e8c65b846468fd2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.5
|
Release files / avendesora_export-0.2-py3-none-any.whl
| Download URL | avendesora_export-0.2-py3-none-any.whl |
|---|---|
| Size | 15.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7f0b41c8fe88b462f1604dd00fc248c8e6cfeeb3fb489d4ca2b81dc61c39e2d5
|
|
BLAKE2b-256 checksum How to use checksums |
b52ad68edfa14e85d31ebffbd758cd647fda1e713959dff2ede16571a6b3412d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.5
|
Security for avendesora-export 0.2
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.