-
Why not just install the web apps straight on the OS, and use NGINX config to direct traffic appropriately, based on the host name?
Because then you have your temporary piece of work leaving permanent files on your OS.
Over time this cruft is messy, and when you're working with multiple web apps it's hard to divine which left what where.
Docker is fantastic for local development in the same way virtualenv is. It can namespace and contain all of the files, processes and configuration for an app.
When you're done with it... just blow it away.
Then if you're deploying it can be a dream there too. Maintain your own company image repo and have your CI push docker images into it. Later... just deploy a pushed image to whatever container cluster you happen to run in prod, be it Kubernetes, Mesos, etc.
The experience remains consistent from dev through to prod, and the only thing we really gained is better management.
But that's ace, better management is what was missing.
-
I'm not very good and often break things while trying to sort stuff out. I like that with docker I can stop the container, remove it and start from scratch in very little time without worrying I've broken some other dependencies or anything like that.
I'd guess I'd need to run a dhcp server, dns server and nginx all up and running.
I'm rebuilding my home server. I used to use amahi which was some software built on ubuntu. It set a lot off stuff up for you. I never really liked it though, so I'm trying to start from scratch. I have just discovered docker. Has anyone experience of this? The containers are easy to set up but what i would like to do is use my server as a dns server so that i can access web-apps on the server by a name rather than IP and port number. Can anyone offer any advice?