Using multiple bind mounts with private repositories enabled
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 38/100
Research direction
Start by reproducing the setup with the rest-server Docker image, two host disks mounted at /data/sda and /data/sdb, and private repositories enabled. Compare repository creation using the sda and sdb URL paths with the working non-private configuration. Done means both mounted paths support the documented private-repository URLs, or the path restriction is clearly documented if that behavior is intentional.
Written by the indexing model from the issue text.
Description
Output of rest-server --version
restic/rest-server | latest | e4fb8546f625 | 8 months ago | 15.3MB
Problem description / Steps to reproduce
My setup includes two separate bind mounts (which are actually 2 separate disks attached to the host), which I mount into /data such that I have something like /data/sda and /data/sdb` inside the container. What I want to do is to have separate sets of repositories in these two locations.
Expected behavior
With private repos enabled, I should be able to create a repo using rest:https://user:pass@fqdn/sda/repo and/or rest:https://user:pass@fqdn/sda/user/repo.
Actual behavior
If I don't use private repositories, I am able to create repos with rest:https://user:pass@fqdn/sda/repo or rest:https://user:pass@fqdn/sda/user/repo. However, if I enable private repos, neither of those work, only rest:https://user:pass@fqdn/user/repo.
Do you have any idea what may have caused this?
No. I imagine the code is enforcing some sort of path requirements with private repos?
Did rest-server help you today? Did it make you happy in any way?
Yes, I am really happy with this project. This combined with backrest is ❤
- Dominant language
- Go
- Stars
- 1.5k
- Forks
- 178
- Avg merge
- 15d 9h
- Merged PRs (30d)
- 2
Contributor guide
No contributing guide indexed for this repository
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 · 2 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 unused Open
Difficulty 4/5 3-5 days Newbie friendliness 50/100
restic/rest-server#383 · 2 comments ·
All issues in restic/rest-server
Similar issues
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
blinklabs-io/bursa#904 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
yanet-platform/ipfw-go#129 ·
-
bug confmap/provider/googlesecretmanagerprovider needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
open-telemetry/opentelemetry-collector-contrib#51273 · 2 comments ·
-
bug: AI Gateway client filter lists "Unknown" twice when NULL and literal Unknown clients coexist Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 90/100