You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
Andreas Zweili 33ea4b9386 add test for unreachable server 1 week ago
docs remove the old table 1 week ago
restic_qt get only the snapshots for the current system 1 week ago
scripts rename all references from borg to restic 1 week ago
tests add test for unreachable server 1 week ago
.gitignore rename all references from borg to restic 1 week ago
LICENSE clone borg-qt 6 months ago
MANIFEST.in rename all references from borg to restic 1 week ago
Makefile rename all references from borg to restic 1 week ago
README.md rename all references from borg to restic 1 week ago
requirements.txt clone borg-qt 6 months ago
setup.py rename all references from borg to restic 1 week ago

README.md

Restic-Qt

Restic-Qt is a Python 3 based graphical frontend for the backup tool Restic as its name implies it is using the Qt5 Framework. Currently it works only on Linux.

Motivation

I think Restic is a great backup tool which should be available to many more users. Since command line tools can be a bit scary for less experienced users I decided to write a GUI as my “thesis” during my final semester at the IBZ school in Aarau, Switzerland.

Getting Started

These instructions will get you a copy of the project up and running on your local machine.

Prerequisites

You need to have Restic installed in order to have Restic-Qt working. You can get a binary for your operating system here: https://github.com/restic/restic/releases

On a Debian based system you can install it by copying to ~/.local/bin/. Restic needs to be able to get executed by calling the command restic.

cp ~/Downloads/restic-linux64 ~/.local/bin/restic
chmod +x ~/.local/bin/restic

For other systems check their documenation.

Installing

  1. Installing Restic-Qt is very simple. Download the binary for your operating system here: https://github.com/resticqt/restic-qt/releases or install it with pip:
pip3 install restic-qt
  1. Copy the config file from docs/restic_qt.conf.example to ~/.config/restic_qt/restic_qt.conf and edit it to contain a valid path to your Restic repository and the password. Put all your changes into the [resticqt] section. As of now there is no automated way to setup Restic-Qt.

  2. Run the binary by double clicking on it or by copying it to ~/.local/bin/ like Restic. If you do that you might want to create a desktop file for it. Puth the following code into a restic-qt.desktop file in ~/.local/share/applications/.

[Desktop Entry]
Version=1.0
Name=Restic-Qt
Exec=/home/username/.local/bin/restic-qt
Terminal=false
Type=Application
Categories=Tools
MimeType=x-scheme-handler/tg;

Make sure the file is executable:

chmod +x ~/.local/share/applications/restic-qt.desktop

Now you should find Restic-Qt in your desktop’s start menu.

If you installed Restic-Qt with pip you can either run restic_qt from the command line or edit the desktop file to exec restic_qt instead of the full path.

Development

To start working on Restic-Qt first clone the git repository and install Restic as described in [Prerequisites].

git clone https://github.com/restic-qt/restic-qt.git

Now create a virtual environment.

cd restic-qt
python3 -m venv venv

And activate it.

source venv/bin/activate

Finally you can install Restic-Qt and it’s dependencies.

pip3 install -e .

You’re now all set to work on Restic-Qt. It’s a good idea to run the tests before starting. You can do this with the following command from the root of the repository.

make test

To make testing the application while programming a bit easier there’s a script which reloads the application everytime a file changes in the restic_qt directory. You to use it run the following command from the root of the repository.

./scripts/debugging.sh

ToDos

To have a look at all the planned tasks you can have a look at the planned features here: todos.md

Used packages

Contributing

Everyone is welcome to submit pull requests and reports issues. Please follow PEP8 and remove unnecessary white space when you contribute code. And most importantly make sure that you don’t break any tests and if possible write tests for your code.

Versioning

Currently there is no versioning as such. In the future a versioning scheme based on semantic versioning might get used. The master branch is considered to be the stable branch. Other branches might be highly experimental.

Authors

License

This project is licensed under the GPLv3 License - see the file for details.

Acknowledgments