Currently there isn't any (or I can't find one) option (environment variable, etc.) to set the IP address that mikopbx's services would on BEFORE first start & initial setup.
To give you some context: I'm trying to host the container/docker version of mikopbx on a machine that itself hosts many different containers. Those are separated by utilizing multiple host & container networks so that things do not overlap.
Mikopbx, however, doesn't seem to care about network stuff all that much and starts everything at 0.0.0.0:PORT. IMHO this is a no-go; there should be an option to set the listening address before any software is even running.
So: is it actually possible to configure the listening address (especially if running mikopbx as a container) before starting mikopbx, e.g. with an environment variable? If not, could this issue be considered a feature request for that?
IMHO it would also be a good idea to listen on localhost (127.0.0.1) by default, not on all addresses (0.0.0.0).
Currently there isn't any (or I can't find one) option (environment variable, etc.) to set the IP address that mikopbx's services would on BEFORE first start & initial setup.
To give you some context: I'm trying to host the container/docker version of mikopbx on a machine that itself hosts many different containers. Those are separated by utilizing multiple host & container networks so that things do not overlap.
Mikopbx, however, doesn't seem to care about network stuff all that much and starts everything at
0.0.0.0:PORT. IMHO this is a no-go; there should be an option to set the listening address before any software is even running.So: is it actually possible to configure the listening address (especially if running mikopbx as a container) before starting mikopbx, e.g. with an environment variable? If not, could this issue be considered a feature request for that?
IMHO it would also be a good idea to listen on localhost (
127.0.0.1) by default, not on all addresses (0.0.0.0).