Show me the reason!

When there is an error in the middle of a backup it is difficult to find the reason to why the backup fails. To make it easier to find the reason and potentially remedy we save the error and print it at the end.

Carry it to the end

When an error happens in the backup script the script will exit with a non zero exit code. During execution of a 'blubee backup' command the backup script is run multiple times and the exit code is ignored. This results in an exit code of 0 from the command even if there were errors during execution.

This behavior hides the errors in the output and may give the impression that all files were backed up successfully. We consider this a fulty behavior.

Know who exits the building

Blubee continues to backup the items in the 'backup.json' even if there is an error with some item. This is useful as a partial backup is often
better than no backup. However, when there are alot of items to backup the error might be hidden in the output and the user may not be aware
that something went wrong. Especially if one is using blubee in a script, as the final exit code of blubee will be 0. To avoid this we make sure to detect when ever an item fails to backup and exit with an approperiate exit code, to notify the caller that something went wrong. To make it easier to find the error we also provide some logs that may help the user identify the issue.

Fixing Space!

Blubee would miss some paths which had spaces, this should be fixed in this release.

Behind bars? No problem

Previously blubee was not able to backup to a server on any other port than the standard 22 for ssh. This release introduces the destination_port option in the backup.json which allows blubee to connect to a custom ssh port.

Same backup? Same time!

For a run with multiple backup configs, blubee would put a datetime-stamp on a backup corresponding to when it started that particular backup config. It is more natural (especially if one wants to restore all configs from a particular run) if all backups, generated from a single run, have the same datetime-stamp.

Allow '/' in root property of backup config

Providing a single slash '/' as the root of a backup config would previously result in a warning message and blubee skipping that backup config. However there are plenty of use cases where one might want to backup something from say /var and /etc in the same config, in which case you need to use / as the root. Now you can! :)

Blubee Supports Arch

Blubee can now be built for Arch, blubee builds something similar to an AUR package that can be packaged and installed with makepkg(and optionally pacman -U). These files can be found in dist/blubee_<version>_all after one runs the build script.

The default backup directory for deleted and changed files during restore has moved from /var/local to /var/lib.

Spaces and unorthodoxy

With this release one may now define paths in ones backup configs that contains spaces
and/or unorthodox characters such as '@!åäöØÆ%' etc.

We can now build a tar ball as well as a *.deb, and the file permissions should be
correctly set to root.

Blubee version 1.0.0

Release of Blubee version 1.0.0

Version 1.0.0 can:

• backup local->local and local->remote
• restore local->local and remote->local
• dry run for backup and restore
• pass custom config
• choose backup config to backup/restore
• choose which datetime stamp to restore

If you use the *.tar.gz don't forget to create the default directory for backing up files that would be changed or deleted during restore /var/local/blubee/backups as described in the "Manual Install" section in the README.md.