Rishabh Mishra

The instance-type naming is the part worth slowing down on for a first deploy. I would start with the smallest size that fits the workload, then size up from real CPU and memory use, rather than guessing a large instance up front.

Agreed. I would frame it as a trade-off, not a shortcut: a one-minute gate that always runs beats a thorough one that gets skipped. The fast check should cover the failure that would hurt most, and the rest can live in a slower review.

The saved-plan rule is the part I would keep. Applying exactly what was reviewed removes a whole class of surprises. I would also keep each plan artifact tied to its run, so a re-run cannot quietly apply a newer change.

That is the real test for it. A check people skip under pressure is not a gate, even if it is thorough on paper. Keeping it to one minute is what makes it survive a busy deploy day.

A useful comparison. For small projects, I would keep real secrets out of the image and out of any env_file in version control, and use environment: only for non-secret config that changes per deploy.

Exactly, and a small page also makes the check quick to run before each deploy. Keeping one example per tag should stop it from growing back quietly.

Thanks, Anish. That diff check stays valuable only if the dashboard stays clean as more jobs are added, so keeping one example per tag is a good guardrail.

That is the real win, Anish. Checking the tag in the same diff catches a mismatch before it ships. Keeping the page to one example per tag also keeps that check quick as more jobs are added.

Exactly, Anish. Reviewing any new tag in the same pull request that adds the job would keep that short page enforced, so a variant cannot slip in unnoticed.

The template-first point is the one most small sites miss. I would also keep the form message short and ask for a reply, since a reply opens the 24-hour window for a normal follow-up.