Organise env variables and authorization #60
Merged
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.
Description
Spreading the use of environment variables across source files is messy and unmaintainable. Let's compact them into a single file, and use Zod to validate them upon service start up.
Asserting that authorization must be done by the user service creates a tight coupling between services. Let's pass the JWT_SECRET to each service, such that
Given that authorization is now handled within each service, let's
Checklist
Screenshots (if applicable)