-
Notifications
You must be signed in to change notification settings - Fork 19
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
Add Unix domain socket support. #25
Conversation
This adds an optional boolean-valued configuration file option "unixsocket". When specified, it changes the meaning of "listenport" to indicate the path to a Unix domain socket on which prosody-filer should listen, instead of a TCP port. This is useful for multi-user shared hosting environments, where listening on loopback TCP sockets may allow other, unrelated users to connect to the filer.
You might want to checkout my PR from a while ago (now conflicting, but I'll try to rebase it soon). The goal was also to allow unix sockets, but is based on systemd (which, according to your username, you probably don't use? 😜). |
The box where I'm running |
systemd's socket activation functionality is very similar to the traditional Unix My changes are compatible with systemd inasmuch as they don't do anything which conflicts with systemd; they just don't use any systemd-specific functionality. (As it happens I have more than one instance of
) |
@sysvinit I like your approach! And yes, it all works side by side, I'll just have to make some changes to my PR later. Anyway it's a good idea to leave the choice to the user, I don't know if packagers are usually opinionated about systemd vs. "manually configured" network services, in case this project aims to eventually make it into distro repos. Also, happy holidays! 🎅 |
Details in the commit message.