quick-dev-env-setup/
│
├── README.md
├── Brewfile # Lists all packages and casks for brew bundle.
├── setup-dev-environment.sh # Bash script for macOS/Linux/WSL with progress bars
└── setup-windows-oneclick.ps1 # PowerShell script for Windows with progress bars
This repository provides a quick setup for anyone setting up a development environment on a new machine.
| OS | Script |
|---|---|
| Windows 10/11 (via WSL) | setup-windows-oneclick.ps1 |
| Linux / WSL (Ubuntu) | setup-dev-environment.sh |
| macOS (Homebrew) | setup-dev-environment.sh |
- Visual Studio Code
- Git
- GitHub CLI (
gh) - Docker
- Terraform
- Node.js (LTS via NVM)
- Python 3.11+
- Kubectl
- Helm
- AWS CLI
- tldr pages
- Open PowerShell as Administrator.
- Run:
Set-ExecutionPolicy Bypass -Scope Process
.\setup-windows-oneclick.ps1The script installs WSL (if missing), Git, and runs the Linux/macOS setup script automatically in WSL. Watch progress bars and colored messages. Logs are automatically saved.
- Open Terminal.
- Run:
chmod +x setup-dev-environment.sh
./setup-dev-environment.shThe script detects your OS, installs all required tools, shows progress bars, and logs everything automatically.
After installing tools, setup-dev-environment.sh walks you through the setup steps that can't be automated with fixed values, since they involve your personal identity/credentials:
- Git identity — prompts for
user.name/user.emailif not already set, and configures a credential helper (osxkeychainon macOS, credential cache on Linux/WSL). - GitHub CLI — if
ghisn't authenticated, offers to rungh auth login(browser-based device flow). - AWS CLI — if no valid credentials are found, offers to run
aws configure(you'll need an IAM access key/secret from your AWS account).
You can skip any of these prompts (n) and run the underlying command yourself later.
The macOS/Linux/WSL script automatically checks:
git --version
gh --version
docker --version
aws --version
terraform --version
node --version
python3 --version
kubectl version --client
helm --version
code --versionIt also runs deeper health checks:
docker run hello-world— confirms Docker Desktop is actually running, not just installed.npm doctor— flags npm/Node environment issues.
The Windows script (
setup-windows-oneclick.ps1) only verifiesgit,wsl, anddockeritself — full tool verification happens when it runssetup-dev-environment.shinside WSL.
- Each run creates a timestamped log file (
setup-log-YYYYMMDD-HHMMSS.txt) in the same folder. - Use logs for troubleshooting.
- For Windows, always use WSL for Linux-based commands.
- Scripts are beginner-friendly for anyone setting up a new laptop or joining a new team.
- If a tool fails, consult its official documentation.
- Bash script with progress bars and color-coded output.
- Installs all major dev tools (Git, GitHub CLI, Docker, Terraform, Node.js via NVM, Python3, Kubectl, Helm, AWS CLI).
- Interactively configures Git identity/credentials, GitHub CLI auth, and AWS credentials.
- Logs everything to a timestamped file.
- PowerShell script with progress bars and color-coded output.
- Checks and installs WSL + Ubuntu, Git via winget.
- Copies and runs
setup-dev-environment.shinside WSL. - Logs everything automatically.
- One-click installation for macOS, Linux, WSL, and Windows.
- Color-coded output for success/failure/info.
- Progress bars for each tool to give visual feedback.
- Automatic logging with timestamped files for troubleshooting.
- Verification of all installed tools at the end.
git clone https://github.com/mfaizalbe/quick-dev-env-setup.git
cd quick-dev-env-setup
chmod +x setup-dev-environment.sh
./setup-dev-environment.shgit clone https://github.com/mfaizalbe/quick-dev-env-setup.git
cd quick-dev-env-setup
Set-ExecutionPolicy Bypass -Scope Process
.\setup-windows-oneclick.ps1Watch progress bars for each tool and check the log file if anything fails.