Hello Andrey > Then run a dedicated database container. Don't create problems for yourself, > and you won't have to solve them.
Creating problems for myself -- story of my life haha. XD You are absolutely right though. However, about using a dedicated database container, I didn't want to do it that way because I want the testing of my web applications to be somewhat seamless and not require any configuration changes. The goal is to test the web apps AS-IS without any changes to the code by quickly running a script (so it will be automated). Does that make sense? On Tue, Jul 10, 2018 at 10:21 AM, Andrey Repin <anrdae...@yandex.ru> wrote: > Greetings, Tony P! > >> Hi David. Those are excellent points. Actually, I regret not mentioning my >> purpose in the original e-mail. To clarify, I don't intend to run a host >> mariadb and a container mariadb simultaneously. Also, this is definitely not >> for production. This is primarily for my development environment. I intend >> to test my web applications inside various containers which will all have >> different configurations. > > Then run a dedicated database container. Don't create problems for yourself, > and you won't have to solve them. > > > -- > With best regards, > Andrey Repin > Tuesday, July 10, 2018 17:20:32 > > Sorry for my terrible english... > > _______________________________________________ > lxc-users mailing list > lxc-users@lists.linuxcontainers.org > http://lists.linuxcontainers.org/listinfo/lxc-users _______________________________________________ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
