Include steps to include multiple volume instances to Laravel Storage… #1081
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
KTanAug21
deleted the
revise_laravel_storage_to_add_volume_instances_support_steps
branch
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.
… section
Summary of changes
Revise Laravel Section's Persisting The Storage Folder to include support for attaching volume instances to multiple machines of a Fly App.
Related GitHub and Fly.io community links
n/a if none
Notes
Can I get a check on my use of "volume instances" to refer to volumes of the same name( which are required to be created when dealing with attaching to an app with multiple machines ). In line 36