New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Repository URLs for --private-repos in README #76

moho1 opened this Issue Jul 24, 2018 · 2 comments


None yet
3 participants
Copy link

moho1 commented Jul 24, 2018

The README currently states rest:https://foo:pass@host:8000/foo/bar as a valid URL for user foo when using --private-repos. But when using such a URL rest-server answers with a 500 Internal Server Error (ignored by restic) first and with a 404 Not Found second on restic init.

We could just fix this error in the documentation or enable such multiple repos for one user. There are some corner cases where this may be interesting to have.

Implementing it for some other separator (e.g. '+') would be pretty easy. I thought I need this, so I already implemented it in , but then I found out I don't need it, so I am not opening a pull request here but leave it as discussion. I can happily open a pull request if this is wanted this way.

Implementing it with '/' as separator would be much nicer, but more complex.


This comment has been minimized.

Copy link

ririsoft commented Aug 26, 2018

Indeed I fall into the trap until I realized that in a single repository you can backup several distinct things, thus making the use of several repositories per user useless.
However I agree this should be clarified in the readme.


This comment has been minimized.

Copy link

ruiztulio commented Jan 24, 2019

I was about to open an issue about this, for me is useful.

In my case we have several customers and each one have severals apps, so I end up with something like:



I know I can backup all apps in the same repository for a customer, but having it this ways allow us to:

  • Delete all backups when app is deprecated/deleted in a single command
  • Most of the time when the customer migrate to a different app version we don't need the prev version backups, so it is easier to delete them or upload to amazon glacier
  • Sometimes the customer is not our customer, is a customer of another company using our platform and we want to be able to send them the restic repo in case they want it all (not just a single backup that can be gotten easily)

This can be easily done in the command line, but I don't want to have an instance of rest-server per customer (this would be a solution, but not optimal)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment