@Richard D brilliant idea... i install Docker on my Mac but don't know what to do next.
that is the problem with all the container solutions. people get it installed then dont have a clue what to do next. you are not alone. I have worked with some fairly large companies that did the same thing. "I installed Docker, what do I do next?"
@jim m That would be great! I managed to get a Dockerized app running, but it wasn't pretty. It seems once you have the image, getting it online is mostly a matter of adding it to your repository and deploying it. The thing I thought could be great is the load balancing with shared data...
that is the basic flow. 1) install Docker. 2) build or find a docker image to use (hub.docker.com has a ton of pre-built images that may or may not work for you). 3) tell docker to create a container based on the image in step 2.
you dont have to have you own repository for your images, you can use a third party one like hub.docker.com (or there are others). not most third party repositories (for docker images) allow anyone to use your image. which may or may not be what you are looking for. if you want to host your own repository there are options and most of them are actually docker containers themselves. Yeah I get the funny part of docker repository to host your docker images is a docker image itself. If you use GitLab you can use it as your docker image repository.
putting a load balancer in front of docker container is the ideal way to go. that way you can spin up/down docker containers to keep up with your demand. Now your load balancer can be a docker image itself. there are several out there that are free that work very well. and the separation of the app (Xojo app for us) and the DBase (mysql in your suggestion) should be separate containers that way you can update any component without impacting everything. also it always you to scale up/down as the demand needs.