So, you successfully have your containers and you have started to be able to run containers to do stuff. Brilliant. So let us drop into those containers and run something new. You are probably half way there with your understanding, maybe we could say that you have just opened the door on containers, well, you are just about to step in an see how big the room is! Containers give you great, little, isolated machines that you can do with as you please and then throw away.
So, you have successfully installed Docker. Brilliant! Now, what?! Well, the obvious thing to do is to go about running some containers. The Docker documentation suggests that you should pull and run the Hello World container, and although it is small, there are much better things we can do straight away to start to show the power of Docker.
Unless you have been living under a metaphorical rock you will have heard about Docker. But although lots of people have heard of Docker, far fewer are using it day-to-day and even less in production. In this short post, I am going to go over what Docker (and containers are) and how you can start to get up and running with Docker.
If you have been following the growth of encryption on the web (https) and the fact that you can now get free SSL certificates (much like the one on this site) using Lets Encrypt, there is very little reason for not having your site running https, making your data encrypted between the server and the user, making everyone more secure.
Version control. A saviour of modern development and with everyone using git to manage their code nowadays (at least for the last 5 years) having an understanding of git is an essential part of being a developer. Recently I have become more and more involved in code review, using GitLab, Bitbucket and GitHub to manage code from different developers for different projects.