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
Is there a specific reason why the db is running alongside asterisk inside the container? I think it is common for Docker to separate concerns for a number of reasons?
The text was updated successfully, but these errors were encountered:
You are right. It would be better. I tried to do this before and ended up with a lot of issues because the way things were prepared regarding to dependencies, binaries etc so I gave up spending more time. But surely this would be great!
This is the best way of doing this.
On 16 Nov 2021, at 16:17, Leonard Möller ***@***.***> wrote:
Is there a specific reason why the db is running alongside asterisk inside the container? I think it is common for Docker to separate concerns for a number of reasons?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Is there a specific reason why the db is running alongside asterisk inside the container? I think it is common for Docker to separate concerns for a number of reasons?
The text was updated successfully, but these errors were encountered: