Skip to content
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

Update rails to 5.2.1.1 #167

Merged
merged 4 commits into from
Nov 30, 2018
Merged

Update rails to 5.2.1.1 #167

merged 4 commits into from
Nov 30, 2018

Conversation

maciej-szlosarczyk
Copy link
Contributor

@maciej-szlosarczyk maciej-szlosarczyk commented Nov 30, 2018

@maciej-szlosarczyk
Copy link
Contributor Author

There's a CVE, but it should not affect us in rest-whois.

@vohmar
Copy link
Contributor

vohmar commented Nov 30, 2018

webserver does not start after this update on staging

Error:
Web application could not be started
Error ID:
c691cc05
Details:
Web application could not be started by the Phusion Passenger application server.

Please read the Passenger log file (search for the Error ID) to find the details of the error.

You can also get a detailed report to appear directly on this page, but for security reasons it is only provided if Phusion Passenger is run with environment set to development and/or with the friendly error pages option set to on.

@vohmar vohmar assigned maciej-szlosarczyk and unassigned vohmar Nov 30, 2018
@maciej-szlosarczyk
Copy link
Contributor Author

There was a configuration file missing for a Rails 5.2 feature we don't use, locally with Puma it works so I was not able to discover it before.

It should be fixed now.

@vohmar vohmar merged commit e7d7f69 into master Nov 30, 2018
@vohmar vohmar deleted the update-rails-to-5-2-1-1 branch December 7, 2018 08:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants