When rake tasks need to be part of a deployment, you could find yourself in a situation where the rake task was forgotten about or have to go through the process of shelling into the environment to execute the tasks. In this episode, we look at addressing these issues by creating a way to have rake tasks execute automatically.
Continuing on from the previous episode, we look at creating a Docker Swarm cluster and using Traefik to load balance and route requests to various applications. Using this and CloudFlare proxies, we're able to create and deploy hobby applications in minutes.
I often create Rails projects and while some of these applications are fairly simple, deployment to a production environment still requires a lot of infrastructure setup. In this episode, we take a look at creating a Rails project template and being able to deploy it to a production environment within minutes.
Amazon's newest hosting service, App Runner, makes it fairly easy to deploy web services. In this episode, we take a look at some of the issues with App Runner as well as how we can deploy a Docker container image to the service. We also dive into building Docker images from an Apple M1 computer and pushing to Elastic Container Registry.
I recently upgraded Drifting Ruby's site from Ruby 2.6 to Ruby 2.7 as part of some general maintenance. The Beanstalk instance was using an older version of Amazon Linux. During the upgrade process, I discovered that it wasn't a simple transition. In this episode, we look at the discovery path and how to successfully deploy your Ruby on Rails application to AWS Elastic Beanstalk with Amazon Linux 2 and Ruby 2.7.
Heroku is a Platform as a Service (PaaS), where you can deploy and manage your Ruby on Rails applications. It is one of the easiest platforms to deploy to; allowing you to focus on the development side of things instead of worrying about managing an infrastructure.
Back in Episode #106, we configured and deployed to a very simple AWS Beanstalk environment. However, in this episode, we take things a bit further and explore security groups, an existing database and redis service. Also, there are a few changes that we have to do in order to get Rails 6 working within Beanstalk.