feat: add simplified locations config #280
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #228
Kind of big but I think it's necessary - happy to split this into a few smaller PRs if easier. For now, I'm leaving the
deploy
directory alone. I'll do that when merging #270.Features
locations
concept to config, and a simple way to writing location lists that includesfile://
,s3://
orhttp(s)://
.s3://bucket/prefix
says to find files inbucket
when the request also contains theprefix
-/reads/prefix/<id>
.[]
.use_data_server
anddata_server_path_prefix
.use_data_server = false
has been replaced withdata_server = "None"
.Refactor
Local
config has been renamed toFile
.File
config only inherits scheme and authority values from thedata_server
now. It does not inherit thelocal_path
.data
prefix anymore, which makes the mapping between the initial request and URL tickets clearer.Fixes
Pathbuf
rather than string formating, so config values likefile://data/path
andfile://data/path/
are equivalent.Docs
Build