Let’s explore some alternative for Docker production deployment besides of using AWS ECS and Manual Docker Engine deployment Manual Docker Engine deployment provide us the full details of all the commands to run, but its always better to just run one line of command for ease of deployment, e.g.: docker-machine create -d amazonec2 –amazonec2-access-key UR_AWS_ACCESS_KEY–amazonec2-secret-key UR_AWS_SECRET_KEY –amazonec2-instance-type t2.small –amazonec2-region ap-southeast-1…
We have created our Docker Hub image here and hosted it in a self-provisioned Ubuntu server. What if we want to host it on Amazon ECS (Elastic Container Service) Fargate with the Docker Hub image? Let’s do it: 1. Sign in to AWS Console (if you don’t have an account yet, just sign one up, Farget is billed per minute,…
Continue from Part 1 Now the problem we face now is that we need to stop and re-run the docker image whenever there’s any changes in the Laravel code. To solve this, we can mount the project root into the Docker container’s volume, so it will get the latest code whenever we save the code. To do this, run docker…
It’s kind of pain to SSH into staging server and run git pull whenever there’s any code change in Master repo for testing in the staging server. It would save some time if whenever there’s a push to Master, Gitlab will automatically deploy the latest code to staging server for testers to test it out. It’s confusing as there’s private…