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.
Beginning by this episode we will be trying to examine all the possibilities offered to us by the various AWS SDKs. This time is the turn of PHP‘s SDK, we will explore all the others in times to come.
This tutorial’s code is trivial, you wouldn’t put it into production, it has nothing to do with a modular and OOP style of programming. In spite of its simplicity, it can give you all the key concepts that can guide you through the learning of AWS SDKs.
The first thing I wanna do is to give you some references to start your learning, you will find some interesting stuff in this introduction page of AWS SDK for PHP.
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.
In this simple tutorial I’m gonna teach you some basic tricks about a skinny LAMP application containerized with Docker.
One of the main focuses of Docker is to solve a common problem in developing and deploying complex applications, which is known as “The Matrix from Hell”.
When designing an application stack which is more than trivial, you have to take care of the compatibility between different version of tools and languages and their dependecies, which have to coexist in the same machine.
With Docker, you solve this problem by instantiating different light-weight machines in a single host, without the need to create real virtual machines on the cloud and spending a lot more: a Docker container consumes a lot less resources.