Release SQS for docker-compose.yaml users (includes budi CLI users) #13999
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
…ker-compose-for-sqs
samwho
changed the title
mike12345567
approved these changes
Jul 2, 2024
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.
Description
This PR will release SQS for people using the Docker Compose and Budi CLI self-hosting methods. So the next time that they update, they will have an SQS enabled deployment. This will mean that the first time they load an app after running this update, there will be a one-time migration to make their data compatible with SQS.
Because we're not quite ready to release this into the wild yet, I'm going to leave this PR in a draft state so it doesn't get merged by accident.