Readme | Installation | Requirements | Configuration | Security | Compression | Encryption | Examples | Contributing
- Do report errors when you encounter them
- Do report suggestions for enhancements
- Let me know if this runs successfully on an operating system I have not listed yet (see README)
- Add more exotic compression algorithm when you use them successfully (see here)
- Extend the Example section
Anybody willing to help me get this into
-
brew (OSX homebrew) - yum (CentOS)
- apt (Debian)
- apt (Ubuntu)
- pkg (FreeBSD)
- Extend documentation
- Improve project webpage
- Fix grammatical errors
- ...
Whenever the code is changed or a pull-request is made, travis will trigger many hundred tests against the code and the program operation. All tests must pass without exception in order to accept the pull request.
The first check will run shellcheck
in the most strict POSIX mode, after this test has passed the following will be checked for every single combination of configuration setting:
-
Unbound variable tests (script runs with
#!/bin/sh -u
) -
Syntax error tests
-
Abnormal program termination
-
Abnormal behaviour
-
Error handling and catching ` Apart from this there are many more specific checks, some examples are:
-
Backups cannot be overwritten
-
Proper deletion (
tmpwatch
/tpmreaper
) -
Checks against encryption
-
basically all configuration directives are checked ...
Credit goes where credit belongs. All contributors will be listed on the project homepage in the contributors section.