Use unicorn (instead of webrick) in production #3387
Merged
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.
Starting from Ruby 3.0, webrick is only loadable when it is required as a gem. Our Gemfile did not require it as a gem, but google-apis-core <=0.11.2 happened to have had it as a dependency, so Rails server could successfully load webrick.
#3381 upgraded google-apis-core to 0.11.3, in which version the dependency on webrick was dropped, and that made Rails server fail in trying to load webrick.
However, running webrick in production is not recommended in the first place as it is only for development and testing purposes.
By requiring unicorn-rails, unicorn becomes the default Rails server which is suitable for running in production.