Docker: Allow optional building of the frontend #4986
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.
For Pixelfed users/forks that uses a modified frontend, this will allow them to use the new Docker setup out of the box.
With
DOCKER_APP_BUILD_FRONTEND=0
(default)By default no building will happen, just a couple of minor "wasteful" Docker build steps that are effectively NOOPs.
With
DOCKER_APP_BUILD_FRONTEND=1
npm install --dev
are installed in the intermediate image followed bynpm run production
that builds the frontend.The new/updated files are then copied into the final container image, overriding the default pre-built assets.
Updating
./docker/dottie sync
to update your existing.env
file with the new one./docker/dottie set DOCKER_APP_BUILD_FRONTEND=1
to enable the new settingdocker compose build
to kick off the build processdocker compose up -d
to recreate your containers with the new custom frontend