@nate-sd Interesting, are you storing your database in a directory just below the web root?
I have a similar set up for some testing I did which is the following. It names the sql volume as
ss-mysql-storage and is stored in
/var/lib/docker/volumes which can be viewed, deleted etc via docker commands. Note also it creates a db schema of 'silverstripe-test' if it doesn't exist and sets the root password to... 'password'.
This is the .env to work with the schema created by docker.
Only thing that I didn't understand the reason why is occasional necessity to exec into the web container and run a
./vendor/bin/sake dev/build for the first time the network and containers are created and as such, the init of the schema.
I've got this persistent issue with base url. Viewing pages via admin in split mode, pages load correctly with base url set correctly, but when viewing any page out of admin, the base url gets set to Docker container id resulting in something like http://jkfdi4nfvjkdls:8080/. Any ideas on what could be going wrong?
@stevie has joined the channel
@taoceanz one thing you can do is ensure that you are forcing the base url in configuration in your .env:
otherwise I imagine whats happening is that the proxy or the actual server inside docker is reporting back its base as being the machine name and port its running on there
do you have an example of your docker configuration?