Continuous Delivery Using Docker – A React.js Application

Let’s recap where we are so far:

• In my first post, Getting Docker Running On AWS, I explored what Docker is then walked through the steps to get a hello world web application up on Amazon Web Services.
• In the next post, Docker Hub Hello World, the focus was switched to creating my own image in Docker Hub. This was a manual build.
• Logically, the next post was to automate the build process, Docker Hub Automated Build.

Now, if we know how to create an automatic Docker Hub build, and we know how to do a manual deploy to Amazon Web Services, then, we should be able to kick off an application deploy upon a successful build with a code change in one of our own repositories.

Let’s explore how we can do this with a React.js application.

Docker Hub Automated Build

In my post Docker Hub Hello World, we learned how to walk with Docker Hub. Creating a manual docker build and uploading it was a great first step. But, it’s nothing to brag about yet.

In this post, we will be going through the Docker Hub Automated Build tutorial.

Automated Builds have several advantages:
– Images built in this way are built exactly as specified.
– The Dockerfile is available to anyone with access to your Docker Hub repository.
– Your repository is kept up-to-date with code changes automatically.

So let’s do this!

Creating My First PyPI Package

In my efforts to gulp the cool-aid on all things Python, this weekend I uploaded my first package to PyPI. What is PyPI you ask? When you use pip, the default repository used is PyPI. From the official website:

PyPI — the Python Package Index
The Python Package Index is a repository of software for the Python programming language.

GitHub Commit Message Standardization

A while ago at work, I found myself looking at a pull request and I realized that my commit messages were weak and did not properly convey the intent of the change. This was a weakness, writing meaningful commit messages, I often found myself needing to improve upon. At work, I wrote an email about this back in September.

Just as code should be self documenting, outlining a best practices for commit messages will do the same for pull requests.

From Zero to Continuous Delivery

---

Imagine a world where a code update to fix a defect or add a feature is automatically pushed to a production on commit (or merged pull request) to master! We live in a time where this is now a reality for many companies of all sizes. A few large company examples are: Google, Facebook, LinkedIn, Netflix, and Etsy.