Step 0.5 — See it work before you build it¶

About 10 minutes. Deploy the finished application, look at it, delete it.

You are about to spend a few hours on this. Before that, it is worth ten minutes finding out whether your account, your CLI and your environment actually work together — and seeing what you are aiming at.

Deploy the finished thing¶

Point your branch at the end of the tutorial:

git fetch upstream
git reset --hard upstream/step-14
git push --force origin tutorial

Why step 14 and not step 17

Step 14 is the last state that works on every environment. Step 15 splits the frontend onto a path, which needs path-based routing switched on where you are. If yours has it, use step-17 instead — you will see the same thing, on one URL.

Then:

mecca register <your repository URL> -b tutorial
mecca app redeploy tally-preview -b tutorial

Watch it happen¶

mecca queue list

You will see rows appear and change state. That is the whole model in one screen: you do not perform actions, you request them, and the platform works through a queue. Steps 2 and 3 teach you to read this properly.

When it settles:

mecca app show tally-preview -b tutorial

Open the URL it prints. You should get a roadmap board with three columns, a vote button on each card and a form at the bottom. Submit an idea — it appears a moment later, because a background worker wrote it.

That single page has a React frontend, a Python API, a worker, Postgres and Redis behind it. You declared none of that; the repository did, in about ninety lines of YAML.

Now delete it¶

mecca app delete tally-preview -b tutorial

This is a full purge — containers, database, drives, routing, history. It is not reversible, which is why the tutorial has you do it once now, deliberately, on something you do not care about.

If any of that did not work¶

What you saw	What it usually means
`mecca: command not found`	The install did not put it on your PATH. Reopen your shell.
Anything about not being logged in	`mecca login`
The register step complains it cannot read the repository	Your fork is private, or you pushed the branch to the wrong remote. `git push -u origin tutorial`.
The deploy never leaves the queue	`mecca queue diagnose <id>` — it explains, in a sentence, what it is waiting for.
The URL loads a login page	The app is private, which is the default. That is step 2.

Now start properly: Step 1 — Deploy it.