Recommended docker tutorial for working with large web packages?
All, Does anyone have a favorite link that explains the "midlevel" management of large web projects with docker. I have searched and read, but I seem to be just getting disjointed bits of basic how to or being stuck in the full docker.com reference. I have the basics, I can pull, attach, detach, exec, restart, manage IDs, for normal single apps, etc..., but I'm flummoxed trying to sort out and get eGroupware configured and running in docker with docker-compose and the 10 other apps it pulls in, collabra, rocketchat, swoolepush, etc... docker compose pulls everything and sets it up and running, but all I can get back from nginx over :8080 is "I'm working, but the page has permanently moved..." Nothing on the other exported port of :4443. So far I've ended up with 5 source trees of eGroupware in /var/lib/docker/... in 4 volumes and 1 overlay for the various configs I've tried with intervening 'docker compose up' and 'docker compose down'. Worth a chance to ask if someone has a favorite link or howto that discusses docker at that level that not on page 227 of the full manual. (yes, I would use the opensuse package, but the server I'm working with is running Arch, and all the egroupware folks cater to in their howto's is Ubuntu -- though why it matters for a container is odd, but it does, and unfortunately the traditional egroupware web-install is no longer actively supported - while it still works it quite flaky due to push-notifications replacing normal Ajax or js page update and the push implemented only works within the container.) Any suggestions welcomed, in the meantime I'll keep plowing through the docker.com reference material... Oh joy... -- David C. Rankin, J.D.,P.E.
On 9/29/23 22:40, David C. Rankin wrote:
Any suggestions welcomed, in the meantime I'll keep plowing through the docker.com reference material... Oh joy...
One thing this exercise has taught me is you can make anything work in a container -- but it isn't worth a crap if you can't use it from outside the container. It's a bloody nightmare. And, 10G worth of downloads for 220M of application is just nuts.... The other thing that is abundantly clear is the container adds a whole new world of complexity to using anything inside it. Especially if you need to customize what's in the container in any slight way. It basically a take what they give or leave-it proposition, or be prepared for an extensive and steep learning curve akin to learning the nuances of all the various contained packages and the container all at once. It will kill the Linux enthusiast. I may be its first victim.... -- David C. Rankin, J.D.,P.E.
participants (1)
-
David C. Rankin