Tutorials
Hands-on, end-to-end walkthroughs. Where the Developer Guide explains features one at a time, tutorials take a real (small) app from zero to a running, connected deployment.
Prerequisites
Before any of the stack tutorials, make sure your platform is set up to build and deploy a Git-based app:
- Connect a Git provider. In Settings → Git Providers, connect GitHub (or GitLab/Bitbucket/Gitea) and finish the install/authorization — a provider showing "Action Required" isn't usable yet and won't appear in the deploy dropdown. See Deploy Your First App.
- Configure a Build Registry — two steps. Git-source apps build a container image that needs somewhere to live; without one you'll see a "Registry Required" warning. First add a registry in Settings → Registry, then assign it to each service on its Advanced → Build Registry tab. Adding it in Settings alone is not enough — the build pushes to the registry assigned on the service. See Container Registry.
With those in place, pick a tutorial below.
When you create an Application, a Set up your application wizard opens and walks you through it in order — source → build → port/domain → build registry → deploy — so you don't have to hunt across tabs. Closed it, or came back later? Reopen it any time via Finish setup on the service's General tab while setup is incomplete.
Prefer the manual route? Just close the wizard and use the tabs. Each section (Provider, Build Type, …) still has its own Save button — but switching tabs with unsaved edits now prompts you before discarding, so nothing is lost silently.
Deploy a Stack
Each of these builds the same two-component app — a web service talking to a database — using Stacks, in a different language. Pick the one you know:
- Python (Flask + PostgreSQL)
- Python (Django + PostgreSQL)
- Node.js (Express + PostgreSQL)
- PHP (Apache + MySQL)
All follow the same shape: create the services, group them into a stack, draw one connection so the platform injects the database credentials, and deploy the whole thing in one click.