Enable Tigris support for Laravel apps #3866
Merged
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
… set the proper secret names to use for tigris extension
3 tasks
KTanAug21
deleted the
enable_tigris_with_custom_secret_key_names_for_laravel_apps
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.
Change Summary
What and Why:
Enable tigris extension for Laravel fly apps, and use the proper secret names for integrating the extension.
This PR is created so that users deploying their Laravel apps to Fly.io can automatically get Tigris configured for their Fly app.
How:
Related to:
#3833
https://flyio.slack.com/archives/C042W39VAMB/p1721229461279579
Documentation