Docker Heroku #529
Open
Docker Heroku #529
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
This allows us to run legacy ruby versions such as 2.7 that are not permitted on other regular heroku stacks.
benlovell
force-pushed
the
docker-heroku
branch
from
7aaaefb to
1cf6cfa
Compare
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.
This is the bare minimum required to continue to run the CMS instances on Heroku using the legacy 2.7 Ruby. The new container stacks do not permit Rubies of this vintage and will entirely EOL Ruby 2.7 by May 25, meaning we will no longer be able to run with these in production. The effort required to upgrade the Ruby versions is big, especially against the backdrop of these apps becoming EOL soon after being replaced.