You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Make relative unix sockets absolute by making them absolute against the AppWorkPath
Fix#17833
## ⚠️ BREAKING ⚠️
Prior to this PR relative unix sockets would have been asserted to be relative to the current working directory that gitea, gitea serv, hook and manager etc were running in. Hooks and Serv would have failed to work properly under this situation so we expect that although this is a technically breaking change the previous situation was already broken.
Signed-off-by: Andrew Thornton <[email protected]>
Copy file name to clipboardExpand all lines: docs/content/doc/advanced/config-cheat-sheet.en-us.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -247,7 +247,7 @@ The following configuration set `Content-Type: application/vnd.android.package-a
247
247
-`HTTP_ADDR`: **0.0.0.0**: HTTP listen address.
248
248
- If `PROTOCOL` is set to `fcgi`, Gitea will listen for FastCGI requests on TCP socket
249
249
defined by `HTTP_ADDR` and `HTTP_PORT` configuration settings.
250
-
- If `PROTOCOL` is set to `unix` or `fcgi+unix`, this should be the name of the Unix socket file to use.
250
+
- If `PROTOCOL` is set to `unix` or `fcgi+unix`, this should be the name of the Unix socket file to use. Relative paths will be made absolute against the AppWorkPath.
251
251
-`HTTP_PORT`: **3000**: HTTP listen port.
252
252
- If `PROTOCOL` is set to `fcgi`, Gitea will listen for FastCGI requests on TCP socket
253
253
defined by `HTTP_ADDR` and `HTTP_PORT` configuration settings.
0 commit comments