systemd-socket-activation: Let systemd bind the server's socket for you

[ library, mit, network, system ] [ Propose Tags ]

"Socket activation" is the a feature of systemd. We use it for web servers, to avoid the momentary downtime that otherwise occurs while restarting processes. Because the socket is manged by systemd, not by our process, the socket remains even while our process is down. Requests to the socket are queued until our process comes back up to respond.


[Skip to Readme]

Downloads

Note: This package has metadata revisions in the cabal description newer than included in the tarball. To unpack the package including the revisions, use 'cabal get'.

Maintainer's Corner

Package maintainers

For package maintainers and hackage trustees

Candidates

  • No Candidates
Versions [RSS] 1, 1.0.0.1, 1.0.0.2, 1.1.0.0, 1.1.0.1
Change log changelog.md
Dependencies base (>=4.16 && <4.19), containers (>=0.6.4 && <0.7), network (>=3.1.2 && <3.2), quaalude (>=0.0.0 && <0.1), text (>=1.2.4 && <1.3 || >=2.0 && <2.1), transformers (>=0.5.6 && <0.7), unix (>=2.7.2 && <2.9) [details]
License MIT
Copyright 2021 Mission Valley Software LLC
Author Chris Martin
Maintainer Chris Martin, Julie Moronuki
Revised Revision 1 made by chris_martin at 2023-06-01T17:41:26Z
Category System, Network
Home page https://github.com/typeclasses/systemd-socket-activation
Bug tracker https://github.com/typeclasses/systemd-socket-activation/issues
Source repo head: git clone https://github.com/typeclasses/systemd-socket-activation
Uploaded by chris_martin at 2023-02-26T00:32:53Z
Distributions LTSHaskell:1.1.0.1, NixOS:1.1.0.1
Downloads 424 total (12 in the last 30 days)
Rating (no votes yet) [estimated by Bayesian average]
Your Rating
  • λ
  • λ
  • λ
Status Docs available [build log]
Last success reported on 2023-02-26 [all 1 reports]

Readme for systemd-socket-activation-1.1.0.1

[back to package description]

"Socket activation" is the a feature of systemd. (documentation)

We use it for web servers, to avoid the momentary downtime that otherwise occurs while restarting processes. Because the socket is manged by systemd, not by our process, the socket remains even while our process is down. Requests to the socket are queued until our process comes back up to respond.