For work this tools, you need configured [megatools](https://github.com/megous/megatools)
pip install BackupMega or for install in user environment pip install –user BackupMega
After configured megatool, can use:
Before start backup you need create file backup-mega.txt in user foled (/home/$USER) and transfer absolute path foledsfiles for backup across Enter `bash /home/user/documents /home/user/.bash_aliases ` And run command in terminal: backup
Metadata
Release files for BackupMega 0.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 | |
|---|---|---|---|---|
| BackupMega-0.0.2.tar.gz | 2.5 kB | Without provenance | Details |
Release files / BackupMega-0.0.2.tar.gz
| Download URL | BackupMega-0.0.2.tar.gz |
|---|---|
| Size | 2.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3a9feca7061a12fb4bbc8775188202db7ec94def7080649cf7fb4f374a805441
|
|
BLAKE2b-256 checksum How to use checksums |
531a727e297f581e5a2b3908d0c23180e548b02dad11bc622f6bf3d161897c2d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for BackupMega 0.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.