{"id":717,"date":"2017-06-11T13:16:57","date_gmt":"2017-06-11T17:16:57","guid":{"rendered":"http:\/\/www.kralidis.ca\/blog\/?p=717"},"modified":"2019-01-31T20:01:58","modified_gmt":"2019-02-01T01:01:58","slug":"hello-docker","status":"publish","type":"post","link":"https:\/\/www.kralidis.ca\/blog\/2017\/06\/11\/hello-docker\/","title":{"rendered":"Hello Docker"},"content":{"rendered":"

For decades now my dev life has been thanks to headless servers in the basement (these days running Debian) which I simply SSH to and work remotely. This has served me well for so long although serious box hugging<\/a> was at play here.\u00a0 Being a reproducible workflow maniac and having virtualenv helped as well.<\/p>\n

Fast forward a few years and add to that mix dev work on my MacBook Pro.\u00a0 It’s 64-bit with an SSD and 8GB of RAM and is great for trips.\u00a0 In this case I was less liberal with installing libraries and packages given it’s a shared computer (I recently had to do a full macOS re-install to fix performance issues).<\/p>\n

Enter Docker.\u00a0 Here I am able to start up a full development environment very easily without affecting my MacBook per se (only a Docker install is required).\u00a0 Publish to Docker Hub<\/a> and done.\u00a0 Pull and run at will. My initial requirements for the repo<\/a> are pycsw<\/a> development, but this will grow over time.<\/p>\n

Of course I’m really late to the party (Sean Gillies thought he was late!<\/a>), and I’m sure there are better approaches, but I think I’m finally feeling Docker. Good times!<\/p>\n\n\n