-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade to rails 7.2 #13
Conversation
|
||
# Force all access to the app over SSL, use Strict-Transport-Security, and use secure cookies. | ||
config.force_ssl = false | ||
config.force_ssl = true |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should really be true. For local testing we can change the RAILS_ENV variable in the docker-compose.yml
file.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested locally with the RAILS_ENV
change in the docker-compose.yml
file.
491e226
to
4d54c54
Compare
# Enables YJIT as of Ruby 3.3, to bring sizeable performance improvements. If you are | ||
# deploying to a memory constrained environment you may want to set this to `false`. | ||
#++ | ||
# Rails.application.config.yjit = true |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This may be something that we need to disable if we run into memory issues.
4d54c54
to
7f6878b
Compare
f16595b
to
8cffe7d
Compare
Sudden CI failure (also on main) seems to be because of docker-library/ruby@7f078b1. It already got reverted in docker-library/ruby@6f84caa, but we may need to wait for it to be released. Let's fix it now: #15 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! 👍🏼
We do not yet have a DB and the migrations are only needed for active storage.
Since we don't use the db yet, it still worked with the wrong PW.
8cffe7d
to
1022c69
Compare
Ticket-22953