Skip to content

Conversation

@dekellum
Copy link
Contributor

@dekellum dekellum commented Apr 1, 2016

Socket activation didn't work for SSL or any listeners specifying additional parameters.

These commits begin with some logging and basic cleanup of the prior socket activation additions. 3030870 fixes socket activation for the additional listener types. And finally I add a docs/systemd.md to give a more complete example of the whole setup.

dekellum added 7 commits April 1, 2016 13:17
  * Keep only the basic known info from imported FD/Socket as keys

  * Then with creating listeners in Binders.parse look for available
    Sockets using only these details.

This allows socket activation to work with ssl and other listeners
where additional parameters are specified in config. These parameters
could not otherwise be determined from an imported FD which previously
caused lookup/matching to fail, followed by failed startup due to
ports being "already in use" (by the same socket activation).
@evanphx evanphx merged commit 0a8c0a2 into puma:master Apr 1, 2016
@evanphx
Copy link
Member

evanphx commented Apr 1, 2016

Thanks!

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