Skip to content

Step 5 — The dashboard, and where things live

About 20 minutes. Branch: step-5. No code changes.

The one new idea: the same state has two faces, and the last label of your URL is your group.

The dashboard

Open the dashboard for your environment and find Tally. You will recognise everything: the deploy you just ran, the queue rows you read with mecca queue list, the logs you read with mecca logs.

It is not a second system. It is a second view of the same database. Anything you do in one shows up in the other. Use whichever suits the moment — the dashboard for looking, the CLI for doing and for anything you want to repeat.

One thing on the dashboard to leave alone: the raw config editor

It writes an overlay that outranks the appmecca.yaml in your repository. Your repo will say one thing, your app will do another, and nothing in the repo explains why.

This whole tutorial rests on your repository is the truth. The overlay breaks that. If you have already used it, clear it before continuing.

Anatomy of your URL

Look at Tally's URL. It decomposes:

tally-tutorial-yourgroup.env.appmecca.net
└─┬──┘ └──┬───┘ └───┬────┘
  app   branch    group
  • the app — what you registered
  • the branch — present because you deployed tutorial. A branch called main is the one that gets no segment, which is why two apps that are identical apart from their branch name can have differently-shaped URLs
  • the group — who owns it

That last one is the piece worth keeping. A group is the unit of ownership: apps belong to groups, membership of a group is what gets you access to its private apps, and cost rolls up to it. It has been in every URL you have opened since step 1.

mecca group show
mecca group list

Two more things to look at now

mecca status
mecca app stats tally -b tutorial

status is health across everything you can see. stats is memory and CPU per container — dull now, with one static site and no containers at all, and the first place you will look once Tally is a real process at step 6.

What you should see

  • Tally in the dashboard, with the same history the CLI showed you.
  • Your group slug, recognised in the URL you have been opening all along.

Reset to the reference

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

That is the beginner track. You can get something live and you can see what the platform is doing. Next: Step 6 — One container, where Tally stops being files and becomes a program.