Finding the right place

For when you know what you want but not where it lives.

Day to day you work with three things, and it helps to know what each is for.

Your AI assistant with gh0stcli is the fastest route for anything you want to do: set up, deploy, or look into why something is stuck. You describe the goal, it checks the current state and proposes the steps.

The portal is where you go for anything you want to know or decide: state, cost, credit, access, and anything that needs approval.

Your repository is where your application is defined. What is in there is what runs. Nothing else.

Rough rule: change things through the assistant and Git; look and decide in the portal.

Common tasks

You want toFastest route
deploy your first applicationask the assistant; it walks you through
update an imagetell the assistant the new tag
connect your own repositoryask the assistant for the guided setup
set up a domain or HTTPSportal, Netzwerk & Exposure
reach an external serviceportal, Netzwerk & Exposure, with a request if needed
add storage or a databaseportal, Storage & Backups
check whether something is runningask the assistant, or look in the portal
check cost and creditportal, Kosten & Nutzung
add someone to the teamportal, Organisation

A sequence that reliably works

  1. Tell your assistant what should be running at the end.
  2. Have it check the current state before changing anything.
  3. Look at what it proposes.
  4. Confirm only the steps you actually want.
  5. Check the result afterwards.

Step two is the one people skip and then regret. "Check the current state first and do not change anything yet" is a sentence that pays for itself repeatedly.

Three things that save trouble

Use the names from your account (namespace, hostname, repository path), not ones that sound plausible. Do not share passwords or tokens in chat; your assistant can walk you through storing them safely. And when an action is not permitted, take the request route offered rather than looking for a way around it.