This tutorial follows another guide that I made, always about Symfony, but this time we’re talking about Symfony 4.
As the framework evolves into new releases there might be some changes in methods, classes and tools. They may become deprecated or obsolete and new tools may be added, although some kind of retrocompatibility may be assured.
If you want to know more about that, you can visit Symfony’s roadmap and discover how it will evolve and how long the various versions will be maintained.
During this short exercise you will learn how to create a simple LAMP example application and deploy it using Docker on the Amazon Web Services ECS platform, with the help of RDS for a MySQL database.
All the following example is based on the AWS CLI, though we could have done faster and easier using the web based console. Instead, having gained a skill with the terminal interface, allows us to better understand how each step and parameter is working. In addition we will be able to create our own automation scripts based on the CLI.
The prerequites for this tutorial are the installation of the AWS CLI and the ECS CLI. If you haven’t them installed on your system, please refer to these links on how to do it: install the AWS CLI and the ECS CLI.
In this short lesson we’re gonna focus on two topics we tackled some time ago in this mini series of tutorials: Laravel and Docker.
In the getting started section of the Laravel project’s documentation we can see that a vagrant box named Homestead is strongly adviced to begin with a quick and smooth developing experience.
Homestead is pre-packed with all the stuff necessary to begin the development of a Laravel application, but when it comes to deploying any application, Docker has many strong points that other virtual environments have not. In many cases it is a must: see this article of mine for further details.
I’m a happy Linkedin user and find interesting the news that Microsoft acquired it; they can make a good couple. And I think it can be a strategic partnership with benefits both for the two companies and for the users.
That said, I think all companies should stay ahead of the rules, and tech giants as well, like Linkedin is.
Following the rules is not just a moral exercise, but a good way, most of the times the only one, to do good business.
In the last two episodes we saw how to create a simple web application using either Symfony or Laravel. Let’s do the same with Ruby on Rails. In this tutorial we’re gonna combine also another competence we developed in this series of tutorials: Docker.
Now that you have all up and running, all you have to do is to create a Ruby on Rails stack on your computer. Let’s start by creating a Docker file, so create a directory named rails_tutorial and put the following content on a file called Dockerfile (without any extension):