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
However, when we tried to deploy that, SELinux would prevent access. First because the socket in /run was labeled var_run_t, but that we fixed by using the apache- prefix, which makes the kernel automatically label it at httpd_var_run_t. Then because Apache is not allowed to connect to an unconfined service (behind that socket):
In #1883 we deployed redmine with Puma using a TCP socket.
From past experience (with Foreman) we know that using an Unix Socket is better performance wise.
To achieve that we need to
In theory, all this can be achieved by the following patch:
However, when we tried to deploy that, SELinux would prevent access. First because the socket in
/run
was labeledvar_run_t
, but that we fixed by using theapache-
prefix, which makes the kernel automatically label it athttpd_var_run_t
. Then because Apache is not allowed to connect to an unconfined service (behind that socket):We gotta label the service correctly (systemd has the
SELinuxContext=
directive for that), but we don't know yet which label would fit best.The text was updated successfully, but these errors were encountered: