And as promised, here is my little surprise. For those of you who follow me, but also for you that visit this website for the first time: here will follow an important consideration.
Whether you are an experienced developer and want to enhance your career, or a newbie, passionate about programming and want to make a living and find job opportunities in the field of software development, take into consideration what I have to say to you.
It may seem nothing, this little gift I intend to share with you, but trust me, it is the result of many years of experience and work in the tech field, so please take a moment to listen to me.
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.
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 this quick tutorial we’re gonna leave the more technical topics to land into the Agile world, a methodology that allows us as startuppers to quickly adapt to frequent and unpredictable changes in projects’ requirements.
The Agile movement takes origin in 2001 from the experience of some prominent Software Developers who taught us some principles in Software Development which can make life easier for developers, deliver value to customers, build successful software projects. Among them we find Kent Beck, Martin Fowler, Robert C. Martin, Ward Cunningham, as first signatories.
You can discover the others, as well as the movement’s 12 core principles at the following website: the agile manifesto.
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):