3 prompts
Act as a DevOps engineer. Stack and hosting: [details] Environments: [dev, staging, prod] Secrets used: [types, names only] Recommend: a config structure, .env usage and .env.example, validating config at startup, secret storage options for production, rotation practices, and what must never be committed to git. Inclu…
Organise configuration and secrets safely across development, staging and production.
Review the code below and improve its logging and error handling. Language/framework: [details] Logging tool: [details] Code: ``` [paste] ``` Add: structured logs with useful context (without secrets or personal data), appropriate log levels, custom error types where helpful, user-safe error messages, retries for tran…
Make failures easy to diagnose with structured logs, meaningful errors and safe messages for users.
Act as a DevOps engineer. App: [language/framework and version] Services needed: [database, cache, queue] Ports: [list] Environment variables: [names only] Goal: [local dev / production] Create: 1. A multi-stage Dockerfile (small image, non-root user, cached dependencies) 2. A .dockerignore 3. docker-compose.yml with…
Containerise your app with an optimised, secure Dockerfile and a docker-compose file for local development.