VITE_API_URL at runtime & optional traefik #1209
Open
+67
−5
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.
Synopsis
This version makes it easier to deploy the fullstack example into cloud services (gcp, aws, azure, etc.).
API endpoint for frontend
Earlier, the argument VITE_API_URL was used at image build time and "hardcoded" into the docker image.
Now it is updated dynamically at container run time, so that deployment (as defined by
.env
) becomes decoupled from the build.One defines the API endpoint for the frontend in the
.env
file withFRONTEND_API_TARGET
.Optional traefik
In the cloud, one might prefer to let the cloud provider to handle ssh, load-balancing, etc. (and also use cloud provider's "native" postgresql). Using traefik or not, can now be defined in the
.env
file with parameterTRAEFIK
:Thanks for the awesome repo & considering this pull request. :)
P. S. I will add this repo as a subrepo into here:
https://github.com/elsampsa/fastapi-fullstack-cloud-deploy/tree/main