Zero-Downtime Docker Compose Deploys Hit HN: What Compose-Native Blue-Green Means for a Self-Hosted PaaS
StatusDude's HN-surfaced guide proves zero-downtime deploys need only Docker Compose, an HAProxy redispatch config, and a ten-line rolling loop — thousands of checks a minute with nothing dropped. Here is the exact recipe, the true blue-green sibling, and the capability gap that appears the moment deploys span machines.
Backstage Scaffolder vs Port in 2026: What a Service Catalog Buys When Your Deploy API Already Owns the Golden Path
Backstage Scaffolder vs Port's managed catalog in 2026: what each adds over a git-push deploy API that already owns the golden path, plus the service-count rule for when a catalog earns its keep.
CI Gets an MCP Server: What TeamCity's and Dooor OS's Deploy-via-MCP Tools Mean for a PaaS API That Agents Still Have to Scrape
TeamCity and Dooor OS now expose builds, deploys, and logs as MCP tools. Here is what they expose, why agents will operate your platform with or without you, and the checklist for a versioned, scoped, auditable agent interface.
Your MCP Deploy Tool's dry_run Flag Is a Suggestion, Not a Lock
MCP tool annotations like readOnlyHint are advisory hints for the client, not enforcement — nothing in the protocol stops a caller from overriding dry_run, tenant_id, or target_environment. A three-line server-side pattern (derive from the session, reject client values, log the attempt) and where host-authority receipts belong.
Headlamp Ate the Kubernetes Dashboard: What Cluster API Operators Actually Get (and What a Git-Push PaaS Should Still Hide)
The Kubernetes Dashboard is archived and Headlamp is the official successor. What the migration changes for Cluster API operators, what the new CAPI plugin delivers, and where a cluster console belongs in a git-push platform.
MCP Joins the Linux Foundation: What Neutral Governance and Server Cards Mean for Shipping a Deploy Server Today
MCP is now neutral Linux Foundation infrastructure with 97M monthly SDK downloads — here is why that plus the stateless 2026-07-28 spec means you should ship your deploy-from-chat MCP server now, and treat Server Cards as a distribution upgrade, not a blocker.
Your Deploy Agent Doesn't Need 100 Tools in Context: Progressive Discovery for Infrastructure MCP Servers
Connecting a deploy agent to a 100-tool MCP server eats the context window before any work starts. A three-tier catalog design keeps agents sharp, with the numbers and spec grounding to back it.
Railpack vs render.yaml vs fly.toml: What Three Deploy-Config Philosophies Teach a Self-Hosted PaaS
Railway detects your stack, Render wants a YAML blueprint, and Fly.io hands you 200 lines of TOML. A side-by-side of all three deploy configs — and why a self-hosted PaaS should pair zero-config detection with a declarative escape hatch.
Render Renamed Every Compute Plan to 2c-4g Style IDs: An IaC Compatibility Checklist Before You Touch Anything
Render's August 26 rename turned Pro Plus into 4c-8g and promised no action required. The grep commands that inventory every plan reference, the three spellings of each plan, the Workflows flex gotcha, and a six-step checklist that proves an IaC fleet is clean.