Related to
Database
Impact
nice to have
Missing Feature
There is no point in forcing the Database connection to use TCP if the DB is on the same host.
It could slightly imrprove performance & security and would avoid firewall rules & NIC overhead.
nc: bad address '/run/postgresql'
Implementation
Seems like netcat is checking if the value of "SEMAPHORE_DB_HOST" points to a TCP-Socket. Allow this to be a Unix Socket file. Maybe use socat?
Design
No response
Related to
Database
Impact
nice to have
Missing Feature
There is no point in forcing the Database connection to use TCP if the DB is on the same host.
It could slightly imrprove performance & security and would avoid firewall rules & NIC overhead.
nc: bad address '/run/postgresql'
Implementation
Seems like netcat is checking if the value of "SEMAPHORE_DB_HOST" points to a TCP-Socket. Allow this to be a Unix Socket file. Maybe use socat?
Design
No response