Document listening on a unix socket #928

New Issue

GiteaMirror · 2025-11-02T03:42:00-06:00

GiteaMirror commented

2025-11-02 03:42:00 -06:00

Originally created by @MTecknology on GitHub (Jul 30, 2017).

It seems that it's only possible to run gitea on a tcp socket. For some configuration deployments, it would be better if gitea could be configured to listen on a unix socket, ideally using something like the wsgi protocol.

Originally created by @MTecknology on GitHub (Jul 30, 2017). It seems that it's only possible to run gitea on a tcp socket. For some configuration deployments, it would be better if gitea could be configured to listen on a unix socket, ideally using something like the wsgi protocol.

GiteaMirror added the type/docs label 2025-11-02 03:42:00 -06:00

GiteaMirror closed this issue

2025-11-02 03:42:00 -06:00

GiteaMirror commented

2025-11-02 03:42:01 -06:00

@silverwind commented on GitHub (Jul 30, 2017):

Why wgsi over a plain http+unix or https+unix socket? Any benefits?

@silverwind commented on GitHub (Jul 30, 2017): Why wgsi over a plain `http+unix` or `https+unix` socket? Any benefits?

GiteaMirror commented

2025-11-02 03:42:01 -06:00

@silverwind commented on GitHub (Jul 30, 2017):

Also, I think this is already supported as of https://github.com/gogits/gogs/pull/2852 by setting HTTP_ADDR to a path and possibly adjusting UNIX_SOCKET_PERMISSION. Should be documented better.

@silverwind commented on GitHub (Jul 30, 2017): Also, I think this is already supported as of https://github.com/gogits/gogs/pull/2852 by setting `HTTP_ADDR` to a path and possibly adjusting `UNIX_SOCKET_PERMISSION`. Should be documented better.

GiteaMirror commented

2025-11-02 03:42:01 -06:00

@MTecknology commented on GitHub (Jul 30, 2017):

If it already exists as http{,s}+unix, that sounds good to me. I didn't find it documented anywhere so I assumed it didn't exist.

@MTecknology commented on GitHub (Jul 30, 2017): If it already exists as http{,s}+unix, that sounds good to me. I didn't find it documented anywhere so I assumed it didn't exist.

GiteaMirror commented

2025-11-02 03:42:01 -06:00

@silverwind commented on GitHub (Jul 30, 2017):

This works for me:

PROTOCOL = unix
HTTP_ADDR = /tmp/gitea
UNIX_SOCKET_PERMISSION = 666

Looks like it only supports http+unix, so I could see it being improved to also support https+unix.

@silverwind commented on GitHub (Jul 30, 2017): This works for me: ``` PROTOCOL = unix HTTP_ADDR = /tmp/gitea UNIX_SOCKET_PERMISSION = 666 ``` Looks like it only supports http+unix, so I could see it being improved to also support https+unix.

GiteaMirror commented

2025-11-02 03:42:02 -06:00

@MTecknology commented on GitHub (Jul 30, 2017):

Awesome! Should I leave this open as a documentation request or should I go ahead and close this?

@MTecknology commented on GitHub (Jul 30, 2017): Awesome! Should I leave this open as a documentation request or should I go ahead and close this?

GiteaMirror commented

2025-11-02 03:42:02 -06:00

@silverwind commented on GitHub (Jul 30, 2017):

I'd leave it open for documentation.

@silverwind commented on GitHub (Jul 30, 2017): I'd leave it open for documentation.

GiteaMirror commented

2025-11-02 03:42:02 -06:00