Packaging & Deployment
Deployment is getting your app off your laptop and onto the internet, where other people can actually use it. Building it is half the job — shipping it is the other half.
The Moving Parts
A few pieces work together every time you put an app online.
- Environments — separate copies for dev, staging, and production
- Containers — package the app so it runs the same everywhere (for example, Docker)
- Config & secrets — settings and API keys, kept OUT of the code
- Hosting — where it actually runs
Keep Your Secrets Out
API keys and passwords go in environment variables or a secrets manager — never committed to git. A key in your repository is a key anyone with the code can read.
Build, Test, Deploy
CI/CD automatically builds, tests, and deploys your app whenever you push a change — instead of you running each step by hand.
Where Builders Host
You rarely need to manage machines yourself. Pick the simplest host that fits what you built.
- Static hosts — for static sites (just files, no server)
- Simple platform hosts — for small servers, without touching the underlying machine
Build It
How to implement: move any hard‑coded key in your project into an environment variable, and add it to a .gitignore so it never gets committed.
- Weekly AI Tasks tracker — your LLM key and messaging‑app token are secrets: env vars, never in the repo. Deploy the small server to a simple host so the webhook has a public URL.
- Personal brand site — deploy straight from the git repo to a static host; every push republishes automatically.
What you learned
Deployment moves your app online. Mind the moving parts — environments, containers, config & secrets, hosting — keep secrets out of git, let CI/CD ship for you, and pick the simplest host that fits.