Download

envGo ships as a single executable per platform. Nothing else needs to be installed — no runtime, no package manager, no dependencies.

Direct downloads

These links always point at the newest release, so they stay valid across versions. Replace latest with a tag such as v1.0.0 if you need to pin one.

Platform	File	Download
macOS, Apple Silicon	envGo-macOS-AppleSilicon.zip	Download
macOS, Intel	envGo-macOS-Intel.zip	Download
Linux, amd64	envgo-linux-amd64	Download
Linux, arm64	envgo-linux-arm64	Download
Windows, amd64	envgo-windows-amd64.exe	Download
Windows, arm64	envgo-windows-arm64.exe	Download

Not sure which you need? Run uname -m on macOS or Linux: arm64 or aarch64 means the ARM build, x86_64 means amd64.

Browse every version at github.com/dnysaz/envgo/releases.

Verify the download

Every release includes a SHA256SUMS file listing the hash of each asset. Download it alongside the binary and check:

# Linux
sha256sum -c SHA256SUMS

# macOS
shasum -a 256 -c SHA256SUMS

# Windows PowerShell, one file at a time
Get-FileHash .\envgo-windows-amd64.exe -Algorithm SHA256

Install

macOS

The ZIP contains the binary plus an installer script:

1. Extract the archive for your chip
2. Double-click Install_envGo.command — it installs to ~/.local/bin/envgo
3. Open a new terminal and run envgo -v

macOS Gatekeeper — “Apple could not verify…”

The ZIP and Install_envGo.command are not Apple-notarized (no paid Apple Developer account), so Gatekeeper shows:

“Apple could not verify ‘Install_envGo.command’ is free of malware…”

This is expected for unsigned open-source binaries. Pick one fix:

A. Right-click Open (fastest):

1. Right-click Install_envGo.command → Open → Open again.
2. Same for the binary if blocked: Right-click dist/envgo-darwin-arm64 → Open.

B. System Settings → Open Anyway:

1. Double-click → Done on the warning.
2. System Settings → Privacy & Security → scroll to Security → click Open Anyway next to Install_envGo.command was blocked… → Open.

C. Terminal — remove quarantine (avoids Gatekeeper entirely):

# For the extracted folder
xattr -dr com.apple.quarantine envGo-macOS-AppleSilicon
# Or for the whole ZIP before extracting via Finder
xattr -d com.apple.quarantine ~/Downloads/envGo-macOS-AppleSilicon.zip

Tip: Extracting with unzip in Terminal instead of double-clicking the ZIP in Finder does not add quarantine at all.

D. Manual install (no script, no warning):

mkdir -p ~/.local/bin
cp envGo-macOS-AppleSilicon/dist/envgo-darwin-arm64 ~/.local/bin/envgo
chmod +x ~/.local/bin/envgo
# add to PATH if needed
echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.zshrc && source ~/.zshrc
envgo -v

If you see envgo cannot be opened because the developer cannot be verified for the binary itself, apply the same Right-click → Open or xattr -dr to ~/.local/bin/envgo.

Why not notarized?

Notarization requires a paid Apple Developer Program membership and an upload to Apple on every release. envGo is MIT, no telemetry, and built with CGO_ENABLED=0 — you can verify via SHA256SUMS and shasum -a 256 -c SHA256SUMS instead, or go build from source (git clone … && make build).

Manual equivalent (same as D):

mkdir -p ~/.local/bin
cp envGo-macOS-AppleSilicon/dist/envgo-darwin-arm64 ~/.local/bin/envgo
chmod +x ~/.local/bin/envgo

Linux

uname -m      # x86_64 = amd64, aarch64 = arm64

sudo cp envgo-linux-amd64 /usr/local/bin/envgo
sudo chmod +x /usr/local/bin/envgo

Or install per-user without sudo:

mkdir -p ~/.local/bin
cp envgo-linux-amd64 ~/.local/bin/envgo
chmod +x ~/.local/bin/envgo

Windows

The .exe is a console application — do not start it by double-clicking, because the window closes the instant the process exits. Use a terminal instead.

Pick the archive matching your CPU (most PCs use amd64):

envgo-windows-amd64.exe   ->   AMD64 (Intel/AMD, most PCs)
envgo-windows-arm64.exe   ->   ARM64 (Surface Pro X, etc.)

mkdir C:\envgo
copy envgo-windows-amd64.exe C:\envgo\envgo.exe

Then add C:\envgo to your PATH. Use either method:

Method A — PowerShell (no admin rights):

[Environment]::SetEnvironmentVariable(
  'Path',
  [Environment]::GetEnvironmentVariable('Path', 'User') + ';C:\envgo',
  'User'
)

Method B — Windows GUI (visual):

1. Win + R → sysdm.cpl → Enter.
2. Advanced tab → Environment Variables….
3. User variables → Path → Edit… → New → type C:\envgo → OK.

Open a new terminal afterwards — changes do not apply to already-open shells. SmartScreen may warn on first run because the binary is not code-signed — choose More info → Run anyway. For the PowerShell installer script, use powershell -NoProfile -ExecutionPolicy Bypass -File .\Install_envGo.ps1 to bypass the default “running scripts is disabled” policy. See the full installation guide for details.

Verify the install

envgo -v     # envGo v1.0.10
envgo -h     # full flag reference

Update envGo

envGo can update itself in place with:

envgo run update

It works the same on macOS, Linux and Windows. The flow:

1. Prints Update envgo to latest version? Y/n and waits for confirmation. Accept with y, yes, or just press Enter (default yes).
2. Queries https://api.github.com/repos/dnysaz/envgo/releases/latest for the newest release.
3. Downloads the matching single binary for your platform — envgo-darwin-arm64, envgo-darwin-amd64, envgo-linux-amd64, envgo-linux-arm64, envgo-windows-amd64.exe, envgo-windows-arm64.exe — over HTTPS.
4. Verifies it against the release’s SHA256SUMS (when present), then runs a startup self-check (envgo -h).
5. Replaces the running envgo binary in place and prints Congrats to new version of envgo!.

envgo run update        # prompts; accept with y

envgo run update never starts a server — it is a short-lived command. On macOS/Linux the replacement is an atomic rename, so a currently running dev server keeps the old in-memory binary until you restart it; the next envgo run dev then uses the new version. On Windows an in-use .exe cannot be replaced directly, so the move is scheduled to run after the current process exits — restart to pick up the new binary.

The downloader sets a User-Agent of envgo/{VERSION} and honors HTTP_PROXY/HTTPS_PROXY from your environment, so it works behind corporate proxies:

HTTPS_PROXY=http://proxy.local:3128 envgo run update

See what would change (no download)

To check the latest version without downloading, compare the printed current and Latest lines, or query the releases page directly:

envgo -v   # current
# latest: https://github.com/dnysaz/envgo/releases/latest

Offline / manual update

If the machine running envgo has no internet access, download the archive or binary from the releases page on another machine, copy it over the old binary in the platform install path (see above), chmod +x it (macOS/Linux), and verify first:

# macOS
shasum -a 256 -c SHA256SUMS
# Linux
sha256sum -c SHA256SUMS
# Windows PowerShell
Get-FileHash .\envgo-windows-amd64.exe -Algorithm SHA256

Next step

mkdir myapp && cd myapp
envgo init
envgo run dev

Continue with the Quick Start walkthrough, or see Installation for the full install reference including uninstall instructions.

What is in each build

All six builds come from the same source and expose identical functionality:

• static file server with path-traversal and dotfile protection
• local-mode /proxy with session token, Host and Origin guards
• public-mode /api/<name> gateway with per-route variable allow-sets, rate limiting, optional bearer auth, and response scrubbing
• .env hot reload
• dashboard, typo detection, PHP execution, and --tls

The Linux and Windows binaries are UPX-compressed to roughly 2–3 MB. The macOS binaries are left uncompressed at roughly 7.5–8 MB, because compressing a Mach-O binary breaks code signing on Apple Silicon.