feat: runtime variables #45
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
manolo-battista
force-pushed
the
feat/runtime-variables
branch
from
2fa627f
to
a25e58f
Compare
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
There was a problem hiding this comment.
license-eye has totally checked 236 files.
| Valid | Invalid | Ignored | Fixed |
|---|---|---|---|
| 145 | 1 | 90 | 0 |
Click to see the invalid file list
- entrypoint.sh
manolo-battista
force-pushed
the
feat/runtime-variables
branch
5 times, most recently
from
de14155
to
d582822
Compare
manolo-battista
force-pushed
the
feat/runtime-variables
branch
from
d582822
to
fd67d90
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
With this update we can follow the philosophy of "Build once, deploy many", using a single builded image we can define the ENV variables on runtime.
The runtime env support is enabled by next-runtime-env package.
The env variables prefixed by
NEXT_PUBLIC_are exposed automatically on client with thewindow.__ENVvariable.Updated the Dockerfile with entrypoint to generate the
__ENV.jsfile. This file is imported with script on head of the application: