Impossible to bind /only/ to unix socket

[wereHamster]

If I start the server with a config where only the unix path is set, it automatically starts listening on the default TCP port (no port specified, defaulting to port 8000). This is an issue for me. I start potentially many servers, each listens on a unique unix socket. There is no way to reliably start them all without also allocating an unused TCP port for each one.

[gregorycollins]

Hi,

You can do this but you might have to avoid using simpleHttpServe (which sets up a lot of these defaults for you) and instead write some config-twiddling code directly. You need to avoid calling completeConfig which is called by extendedCommandLineConfig, and so you'll probably have to configure the server by hand and handle your own command line arguments.

Snap 1.0 should hopefully be easier to configure here.

[wereHamster]

Both simpleHttpServe and httpServe call completeConfig. I'm not very keen on reimplementing the logic inside simpleHttpServe which actually runs the server (rawHttpServe). So while technically possible, it's not what I'd call straight forward to use.

Furthermore, to be able to directly call rawHttpServe it appears one must import at least one function from the Internal module (snapToServerHandler).

[gregorycollins]

I understand all of that -- but if you want it fixed for 0.9 you'll have to work around, and that's what you're going to have to do (internal module and all). I'll make sure that 1.0 supports this use case out of the box.