In a development environment, we probably want to start up/shutdown/pause services or processes without the service daemon restarting again for us.
In a dev or staging environment, once a server is setup, manually or automatically, highly likely there is no need to rerun the autoconfiguration scripts every time the container is restarted.
In a dev or staging environment, once a module (lets say the mysql connector) is available, whether downloaded dynamically or provided statically, highly likely we dont need to redownload it everytime the container is restarted/the startup scripts are run.
This is potentially not just a Restcomm-Docker issue. The autoconfig scripts in RC and RMS will also need to be addressed?
In a development environment, we probably want to start up/shutdown/pause services or processes without the service daemon restarting again for us.
In a dev or staging environment, once a server is setup, manually or automatically, highly likely there is no need to rerun the autoconfiguration scripts every time the container is restarted.
In a dev or staging environment, once a module (lets say the mysql connector) is available, whether downloaded dynamically or provided statically, highly likely we dont need to redownload it everytime the container is restarted/the startup scripts are run.
This is potentially not just a Restcomm-Docker issue. The autoconfig scripts in RC and RMS will also need to be addressed?