Fill/sync restic REST server from local repository
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
No files, tests, or entry points are identified in the issue. Start by reviewing the existing rest-server REST backend API and command-line behavior, then define how a local repository is copied to the server and what completion and consistency should mean; the feature is done when that sync works reliably for the stated backup use case.
Written by the indexing model from the issue text.
Description
Output of rest-server --version
Not relevant here.
What should rest-server do differently?
There should be a command line utility like awscli sync or rsync. Just copy/store the contents of a local repository to rest-server.
What are you trying to do? What is your use case?
You could have a second backup location. So first backup is to your local NAS. There you run prune and so on for faster speed. Then you sync this data to your rest server for restic. This makes it far easier and more secure than using SSH and rsync to update local content of the rest-server.
Basically this should be quite easy to achieve. Perhaps there is already a thirdparty tool for that, that is even compatible with restic rest-server. There are no needs for exclude files, data changed after and other fancy stuff.
Did rest-server help you today? Did it make you happy in any way?
Restic is a really great backup tool. I've restored data multiple times and it always worked as it should. So I can rely on restic backup.
- Dominant language
- Go
- Stars
- 1.5k
- Forks
- 179
- Avg merge
- 15d 9h
- Merged PRs (30d)
- 2
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from restic/rest-server
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
restic/rest-server#389 ·
-
state: need feedback
Difficulty 3/5 1-2 days Newbie friendliness 55/100
restic/rest-server#391 · 5 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
restic/rest-server#390 · 1 comment · 1 reaction ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
restic/rest-server#384 · 2 comments ·
-
Exit after configurable idle period for servers with limited RAM or are off/suspended when unusedOpen
Difficulty 4/5 3-5 days Newbie friendliness 50/100
restic/rest-server#383 · 2 comments ·
All issues in restic/rest-server
Similar issues
-
bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
DataDog/dd-trace-go#5469 ·
Maintainers usually reply within 1 day
-
bug tests
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
l3montree-dev/devguard#3101 ·
Maintainers usually reply within 1 day
-
area:*of bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
oapi-codegen/oapi-codegen#2593 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 85/100
DaoCloud/DaoCloud-docs#7432 ·
Maintainers usually reply within 1 day