chore: add profiles to docker compose to use the local hydra database #74
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.
After using Tabular API with real Hydra data locally I realized the workflow for using TabularAPI locally with real data was not very convenient neither very well documented.
This PR aims to make the DX for this case a bit nicer and better documented, by introducing Docker Compose profiles to manage test and real Hydra database setups.
Changes
--profile test: Starts test CSV database and PostgREST (for tests)--profile hydra: Starts PostgREST connecting to real Hydra CSV database (for development)postgrest-test; mainpostgrestpoints to real HydraPGREST_PORTenv var (defaults to 8080)--profile testNo services start by default; explicitly specify a profile. This allows switching between test and real database setups without separate compose files while always being explicit.