Tung Leo

Automatically generate README.md based on repo structure using Github Action Idea: 1. Loop and detect folder 2. Create relative link on the README.md file 3. Run on Nightly basis

When building python based images for running ./docker practice script we got this err: How to reproduce: `cd devops-basic; ./practice.sh` ``` => ERROR [3/5] RUN pip install -r requirements.txt 181.7s...

Checking for typo, and better organize terraform part.

Reference: https://medium.com/@bradford_hamilton/deploying-containers-on-amazons-ecs-using-fargate-and-terraform-part-2-2e6f6a3a957f

In order to keep the user data, investigate to see if we could have any way to store the related config. Make the container data reusable

**Background:** For now the [dockerfile-lint.yml](https://github.com/tungbq/devops-toolkit/blob/main/.github/workflows/dockerfile-lint.yml#L4) runs on every PRs, but not all PR related to the the Dockerfile. It leads to the duplication issue and watse Github Action resource. **Solution:**...

doc/usage: Demo how to deploy an EC2 instance with terraform/awscli using devops-toolkit

Document improvement tasks. If you find document somewhere in this repo could be improved. Improve it and send us a PR! Thanks