We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
--listen /some/unix.sock
When running a FastCGI responder, we can simply
$ plackup -s FCGI --listen /some/path/to/unix.sock
to have it listen on a UNIX socket. The same is not true for the HTTP version:
$ plackup --listen /some/path/to/unix.sock HTTP::Server::PSGI: Accepting connections at http://0:8080/
This then ends up binding to TCP port 8080, and not the UNIX path.
It'd be great to be able to support UNIX-hosted HTTP responders on fixed paths.
The text was updated successfully, but these errors were encountered:
-s HTTP --listen /some/unix.sock
You may want to look at other PSGI servers, such as Starlet:
❯ plackup -s Starlet --listen unix.sock -e 'sub { [200, [], ["ok"]] }' Plack::Handler::Starlet: Accepting connections at http://0:unix.sock/
Sorry, something went wrong.
Also while there, don't forget to additionally account for chmod, the same issue as miyagawa/Starman#145
chmod
No branches or pull requests
When running a FastCGI responder, we can simply
to have it listen on a UNIX socket. The same is not true for the HTTP version:
This then ends up binding to TCP port 8080, and not the UNIX path.
It'd be great to be able to support UNIX-hosted HTTP responders on fixed paths.
The text was updated successfully, but these errors were encountered: