bupper
bupper badge
travis badge
Simple backup application which allows per-directory backup control by simply including a _BACKUP_THIS file.
How it works
Bupper is very simple: it will recurse through a given directory, looking for a special file indicating that it should be backedup (_BACKUP_THIS), and then it will put that directory into a .tar.gz archive, named after the directory and the current time, and scp it to a given location.
This has few moving parts and works well for a simple household-backup solution, where “whitelisting” a few important directories in your home for backup via transfer to a local network host makes the most sense.
Installation
Assuming Python’s pip is installed (for Debian-based systems, this can be installed with sudo apt-get install python-pip), bupper can be installed directly from PyPI:
pip install bupper
Python versions 3.3+ (and 2.6+) are supported and tested against.
Quick start
Think about how you will configure bupper. The main thing you will want to configure is the --remote flag, which should be remote host and path, or some sort of external storage, that would allow an SSH login:
bupper \ --source '/home/'\ --remote 'backupuser@remote.host:/var/backups/bupper/'
Note: that ‘source’ does not actually back EVERYTHING up in that directory. Instead, it will recursively look for directories that contain a certain filename (_BACKUP_THIS).
Setup bupper with your chosen configuration to run on cron at a regular time (such as daily).
(Optional) Add cron jobs that clean up old backups – this is up to you how you want to do this.
Full usage
usage: bupper [-h] [-d DATE_FORMAT] [-v] [-s SOURCE] [-l LOCAL] [-r REMOTE]
Simple backup script, no diffing or anything fancy.
optional arguments:
-h, --help show this help message and exit
-d DATE_FORMAT, --date-format DATE_FORMAT
date format in strftime
-v, --verbose increase output verbosity
-s SOURCE, --source SOURCE
source directory to scan for bupper configs
-l LOCAL, --local LOCAL
local storage of backups
-r REMOTE, --remote REMOTE
remote storage of backups
Contributing
New features, tests, and bug fixes are welcome!
Metadata
Release files for bupper 0.1.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 |
|---|---|---|---|---|
| bupper-0.1.2.tar.gz | 8.7 kB | Without provenance | Details for bupper-0.1.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| bupper-0.1.2-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details for bupper-0.1.2-py2.py3-none-any.whl |
Total release size: 16.3 kB
Release files / bupper-0.1.2.tar.gz
| Download URL | bupper-0.1.2.tar.gz |
|---|---|
| Size | 8.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0bcdbd4c82f4d4eff0095b270186af14cf67c3906f1bd17dd8edbd9c7e77ef4d
|
|
BLAKE2b-256 checksum How to use checksums |
0321573ffbe3f4a43971207703f4a9db89d020002eb22508d3f653c256b4039e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / bupper-0.1.2-py2.py3-none-any.whl
| Download URL | bupper-0.1.2-py2.py3-none-any.whl |
|---|---|
| Size | 7.6 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
eb92653635dda2d97954698381558f4da76cd08582381afaed6388e16a5bb787
|
|
BLAKE2b-256 checksum How to use checksums |
76fe5116cc030b2090726a587717fea4065f90481d165a3b37d637d566f0c816
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for bupper 0.1.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.