This is the second part of my series on deploying a Django app to Kubernetes.
Click here to read the first part, where I walked through containerizing a Django app and running it on Kubernetes with just the in-memory cache and SQLite database.
There’s a lot of steps to walk through in this tutorial, and I usually don’t get them 100% right myself.
Here are some useful commands to remember if you run into problems:kubectl logs will show the standard output/error of the container, which is usually the first place I look for problems.
This document describes in detail how to achieve this goal, using one of Ansible’s most complete example playbooks as a template: lamp_haproxy.
This example uses a lot of Ansible features: roles, templates, and group variables, and it also comes with an orchestration playbook that can do zero-downtime rolling upgrades of the web application stack.
That’s the software built by server-side scripts, languages that build your site behind the scenes. To provide a seamless experience for the user that’s as close to a desktop application as possible.
There are many server-side languages working toward that end goal.
Instead, we’re going to take a close look at every part of the playbook and describe what it does. This is for site-wide things like yum repository configuration, firewall configuration, and anything else that needs to apply to all of the servers.Continuous Delivery is the concept of frequently delivering updates to your software application.The idea is that by updating more often, you do not have to wait for a specific timed period, and your organization gets better at the process of responding to change.When you type in a URL, lots of code is at work to bring a page to your screen.What connects your site’s database to the browser, creating a smooth, user-friendly experience?