docs: update static deployment guide #19294
Closed
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
The previous .gitlab-ci.yml configuration was not functioning as expected in real-world scenarios. This PR introduces a revised version based on a configuration that has been tested and proven to work in practice. It simplifies the pipeline, improves reliability, and resolves issues encountered with the earlier setup.
|
Duplicate of #19295 |
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.
Summary
The previous .gitlab-ci.yml used node:16.5.0, which caused deployment to fail during the build step due to compatibility issues with vite build.
This PR updates the Node.js version to node:18.16.0, resolving the issue and ensuring the pipeline runs successfully.
Key Changes
Updated Docker image from node:16.5.0 to node:18.16.0.
Ensured the public/ directory is created explicitly during the build process.
Why
The old Node.js version did not support
crypto.getRandomValues, which is required for vite build. The new version ensures compatibility and resolves the deployment failure.