Skip to main content
Platform features need a Cordango workspace. You can sign up here and create one in a few minutes. The open foundation, meaning the CLI, the compiler and the standalone generator, needs no account and is available to everyone.
Everything in Command reference above the publish section works offline. These four commands are the connected half.

​
Get a token

Create a token on your instance under your avatar menu, Personal Access Keys. There are two kinds, and the only difference is how much you have to type.
​
access exchange token
Carries the instance address and tenant inside itself, so the token is the whole command.
​
personal access token
Carries no address, so it needs --instance beside it.
Both mint the same credential and both authenticate identically.
The token’s self-description is checked, never believed. An exchange token says which tenant it belongs to. Login connects to the named instance, asks the server which tenant it actually belongs to, and refuses when the two differ. The address inside a pasted credential is a claim, not authority.
An explicit --instance wins over the address inside the token, because somebody typing it has a reason: a tunnel, a staging host, a local instance.

​
Check where you are pointed

Which instance this workspace publishes to, and as whom. --offline answers from stored credentials without calling the instance.

​
Publish

Three things about how this behaves are deliberate. It builds from source, never from .cordango/. Publishing the last build artifact would let a stale definition reach a real workspace after an edit nobody checked. The artifact is a cache, and a cache isn’t an authority, so publish runs the same pipeline check and build run and sends what that produces. Coherent is the bar, not complete. An app whose domain exists but whose screens don’t is a normal state mid-authoring. Refusing to publish it would make “look at it running” the one thing you can’t do while building. Incomplete apps publish, with the reasons printed. Broken ones don’t publish at all. All or nothing across the workspace. Every selected app is checked before any of them is sent. Publishing three apps and failing on the fourth would leave an instance holding half a workspace whose cross-app references no longer resolve.

​
Disconnect

This forgets a stored credential on this machine. It doesn’t revoke it. Revoke a key on the instance, under the same Personal Access Keys screen that minted it.