In Foreman 2.4 FOREMAN_BIND was dropped and now Puma builds bind statements based on inherited sockets from systemd. That means it's no longer needed to match them. This gives a lot more freedom.
This PR chooses to remove the foreman.socket override if Apache is not enabled. This then uses the default ListenStream from the socket, which happens to be 0.0.0.0:3000 today but we don't really care.
Added by Ewoud Kohl van Wijngaarden about 3 years ago
Refs #29780 - Drop FOREMAN_BIND handling
In Foreman 2.4 FOREMAN_BIND was dropped and now Puma builds bind
statements based on inherited sockets from systemd. That means it's no
longer needed to match them. This gives a lot more freedom.
This PR chooses to remove the foreman.socket override if Apache is not
enabled. This then uses the default ListenStream from the socket, which
happens to be 0.0.0.0:3000 today but we don't really care.