3 ms·

> If anything Docker seemed to make it easier and faster to use and install misconfigured software, not make it easier to get things under control. Hadn't thou

> If anything Docker seemed to make it easier and faster to use and install misconfigured software, not make it easier to get things under control. Hadn't thought about it that way, but I have seen the same thing.

PaulHoule 4y ago
My take is that you can control your environment with Docker and discipline but discipline alone gets you far. Circa 2004 I was maintaining about 80 web sites for a large academic library and not much late 200 web sites for a prolific web consulting firm, plus at least 10 sites on my own account. I came to the conclusion that you could host as many sites with the same software that you like one one machine so long as you can configure: (i) where files are in the filesystem, (ii) how to connect to the relational database, (iii) cryptographic keys. If the server was Apache there was always an Apache configuration file, there would usually be one for the actual application. In a complicated case there would be some templating system that writes all the configuration files. With that kind of system I could frequently get a site up 'n running in a few minutes and there was no difficultly with dev, test, and prod instances or "clon e customer A's site to make a site for customer B". Today it is not that different though the server might be nginx and a system today might have a non-relational database and might have more than one of them and there are probably some API keys. When docker came along me immediate response was "ho hum" and when I tried it first I was stuck behind a slow internet connection docker seemed to be a way to download 3GB of files to make a 3 kilobyte change. I've been at an office with a gigabit connection and it is not so bad but still not so good: it seems fast from an "ops" perspective but from a "dev" perspective it is slow.

3 ms·

> If anything Docker seemed to make it easier and faster to use and install misconfigured software, not make it easier to get things under control. Hadn't thou

by nitwit005 4y ago

PaulHoule 4y ago
My take is that you can control your environment with Docker and discipline but discipline alone gets you far. Circa 2004 I was maintaining about 80 web sites for a large academic library and not much late 200 web sites for a prolific web consulting firm, plus at least 10 sites on my own account. I came to the conclusion that you could host as many sites with the same software that you like one one machine so long as you can configure: (i) where files are in the filesystem, (ii) how to connect to the relational database, (iii) cryptographic keys. If the server was Apache there was always an Apache configuration file, there would usually be one for the actual application. In a complicated case there would be some templating system that writes all the configuration files. With that kind of system I could frequently get a site up 'n running in a few minutes and there was no difficultly with dev, test, and prod instances or "clon e customer A's site to make a site for customer B". Today it is not that different though the server might be nginx and a system today might have a non-relational database and might have more than one of them and there are probably some API keys. When docker came along me immediate response was "ho hum" and when I tried it first I was stuck behind a slow internet connection docker seemed to be a way to download 3GB of files to make a 3 kilobyte change. I've been at an office with a gigabit connection and it is not so bad but still not so good: it seems fast from an "ops" perspective but from a "dev" perspective it is slow.