[feat] Add more prerequisites to a host where development / state generation takes place
- Dominant language
- Shell
- Stars
- 106
- Forks
- 146
- Avg merge
- 21d 40m
- Merged PRs (30d)
- 1
Description
Here are some of the things we needed to install on EC2 instance where we are both running the env (which already has its check-env script) and now we're doing state generation/builds there as well.
1 sudo apt install docker.io docker-compose
8 sudo apt install docker.io
9 sudo apt install podman-docker
34 sudo apt-get install -y ca-certificates curl gnupg
35 sudo install -m 0755 -d /etc/apt/keyrings
41 sudo apt-get install -y docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin
43 sudo apt install docker.io
49 sudo apt install docker-compose
135 sudo snap install gh
136 sudo apt install gh
162 sudo apt install nodejs
165 sudo apt install ripgrep
168 sudo apt install npm
Contributor guide
Research direction
Start by locating the existing check-env script and the setup used on the EC2 host for state generation and builds. Compare its checks with the Docker, GitHub CLI, Node.js, npm, and ripgrep prerequisites listed here; done means the host setup documents or validates the required installations consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, docker, docker-compose, github, nodejs, shell
- Domain
- build-system, devops, infrastructure, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100