Managing Secrets: .env Files, .env.example, and Config in DeployHQ
Posted on
Store secrets safely with .env files and .env.example, then inject them in DeployHQ via the UI, CLI, and API.
Our products pack a punch when it comes to features and it would be easy to miss some of them. Here we post helpful tips & tricks about how to use our products & services.
Posted on
Store secrets safely with .env files and .env.example, then inject them in DeployHQ via the UI, CLI, and API.
Posted on
Project folders let you group DeployHQ projects by client, team, or environment — perfect for agencies taming a crowded projects dashboard.
Posted on
The safe way to give AI coding tools database access: read-only roles, MCP guardrails, and disposable copies. Real GRANT SQL, not hand-waving.
Posted on
Every Sentry issue should tell you which DeployHQ deploy caused it. Two-minute setup, release tracking, regression detection, faster rollback.
Posted on
One API in front of 400+ models. Here's how OpenRouter actually works, how to wire it into your AI coding tools, and where it stops scaling.
Posted on
Decide if your machine can run a local AI coding model — hardware tiers, runtime trade-offs, and how to wire Ollama into Cline, Aider, and OpenCode.
Posted on
Claude Code and Copilot are shifting toward usage-based pricing. Here's how 7 multi-model routers and alternatives compare for shipping teams.
Posted on
Google's eng-practices repo defines what good code review looks like. Here's what each principle means for deployment velocity on teams shipping daily.
Posted on
Why NGINX returns 502 Bad Gateway — upstream timeouts, wrong upstream addresses, FastCGI/PHP-FPM failures, plus SELinux gotchas, with fixes.
Posted on
Disk space, memory, processes, logs — the Linux server commands you reach for before, during, and after every deployment, plus a health-check script.
Posted on
Check your Ubuntu or Linux version from the command line with lsb_release, /etc/os-release, or hostnamectl. Reference + when to use each.
Posted on
Every error in Honeybadger should tell you which DeployHQ release caused it. Wire deploy markers, regression detection, and one-click rollback.