Microteia Console 2.22.1

Installs and updates Microteia in a Firebase project you own. It has no npm dependencies of its own — what it needs are command-line tools that are already on the machine, listed at the bottom.

Installing it

npm i -g @microteia/console
microteia --help

Or run it without installing anything:

npx @microteia/console --help

Where npm's global prefix belongs to root — Node installed system-wide under /usr/local — the global install fails with EACCES. Point npm at a prefix of your own instead of reaching for sudo, which would write root-owned files that then need sudo to remove:

npm config set prefix ~/.npm-global
export PATH="$HOME/.npm-global/bin:$PATH"   # add to ~/.zshrc

This folder also runs as it is, with no npm at all:

node lib/index.js --help

Using it

microteia init --name "<office>"
microteia connect --project <your-firebase-project-id>
microteia unpack --version latest
microteia deploy

connect prints everything that has to be prepared in the Firebase project first — start with the Blaze plan, since nothing else can be created without it.

unpack --version reads the published catalog, downloads the version and checks its sha256 before touching what is installed. On a machine that cannot reach the catalog, name a file you already have:

microteia unpack --kernel <microteia-kernel-x.y.z>.tgz

microteia --version answers what is installed here, and says so when a newer kernel is published.

Later, whenever an office installs an extension that needs server-side resources, run:

microteia provision

The extension shows "Backend pending" in the application until you do, and stays out of the menu.

What has to exist on this machine

| Tool | Used for | | ------------- | -------------------------------------------------------------- | | Node.js 22+ | running this Console (newer is fine; the functions' own runtime is pinned to 22) | | firebase | every deploy — authenticate with firebase login first | | npm, tar | installing the functions' dependencies and unpacking the kernel | | gcloud | creating the App Engine application, and reading which extensions an office installed (gcloud auth login) |

The pack and publish commands in here build and release the platform itself, and only work inside the Microteia repository.

What changed in this Console

CONSOLE-VERSIONS.md, in this folder. unpack copies it into the installation it manages, beside the platform's own KERNEL-VERSIONS.md — each history travels with the artifact it describes.