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
Some servers has unix sockets dedicated to host their services.
For example exposing /srv/http/ directory for users to deploy their services at here unix socket can be added to create https://spdf.myserver.xyz
So in current sitution we use socat to create unix socket at that location which listening for particular port i.e 8080 . /usr/bin/socat UNIX-LISTEN:/srv/http/spdf,mode=660,fork TCP:localhost:8080
And need systemd service file to run this constantly in bg
So this need can be eliminated with Enviromental variable for Systemd service file.
Why is this feature valuable?
For hosting without docker sometimes you need to add two service file
There shouldnt be need to run two systemd service files one for stirling pdf and second for unix socket
There are applications which uses Envirment variable to be added into systemd Service file itself which saves this need.
Environment="SPDF_UNIX_SOCKET=/srv/http/spdf"
Suggested Implementation
Some program like calibre-web provide such env variable eg. Environment="CALIBRE_UNIX_SOCKET=/srv/http/calibre"
We can add similar env var for systemd service file Environment="SPDF_UNIX_SOCKET=/srv/http/spdf"
Additional Information
No response
No Duplicate of the Feature
I have verified that there are no existing features requests similar to my request.
The text was updated successfully, but these errors were encountered:
Feature Description
Some servers has unix sockets dedicated to host their services.
For example exposing
/srv/http/
directory for users to deploy their services at here unix socket can be added to createhttps://spdf.myserver.xyz
So in current sitution we use
socat
to create unix socket at that location which listening for particular port i.e8080
./usr/bin/socat UNIX-LISTEN:/srv/http/spdf,mode=660,fork TCP:localhost:8080
And need systemd service file to run this constantly in bg
So this need can be eliminated with Enviromental variable for Systemd service file.
Why is this feature valuable?
For hosting without docker sometimes you need to add two service file
There shouldnt be need to run two systemd service files one for stirling pdf and second for unix socket
There are applications which uses Envirment variable to be added into
systemd Service file
itself which saves this need.Environment="SPDF_UNIX_SOCKET=/srv/http/spdf"
Suggested Implementation
Some program like calibre-web provide such env variable eg.
Environment="CALIBRE_UNIX_SOCKET=/srv/http/calibre"
We can add similar env var for systemd service file
Environment="SPDF_UNIX_SOCKET=/srv/http/spdf"
Additional Information
No response
No Duplicate of the Feature
The text was updated successfully, but these errors were encountered: