fix: capistrano deployment docs correction for vite v5 #454
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 馃摉
When using Vite v5 and above, Capistrano is not aware that the location of the asset manifest files has moved, and fails on deployment with
Rails assets manifest file not found.
Background 馃摐
When using Vite v5 and above, asset manifest files are output to a
vite/.vite/
subdirectory, by default. Meaning that themanifest.json
andmanifest-assets.json
files that used to reside underpublic/vite/
now reside underpublic/vite/.vite/
.The Fix 馃敤
Update documentation to reflect that there is a difference between the Capistrano configuration when using Vite v4 and Vite v5. The fix when using Vite v5 and above is to set the Capistrano
:assets_manifests
option. The path(s) need to be relative or absolute.