Skip to main content
geoengine push publishes a previously-applied production worker image to Nika’s cloud registry. Once pushed, team members can run the worker directly from their QGIS or ArcGIS Pro plugin — without needing Docker, a terminal, or a local GeoEngine setup.

​
Prerequisites

  • GeoEngine installed and authenticated (geoengine auth login)
  • A production apply completed: geoengine apply (without --dev) — dev builds cannot be pushed

​
Workflow

​
Step 1: Apply in Production Mode

From your worker directory, bump the version in geoengine.yaml if needed, then run a production apply: 
geoengine apply
This builds a versioned image and saves a config snapshot. Dev builds (--dev) are not eligible for push.

​
Step 2: Push to the Cloud

geoengine push [--uuid <worker-uuid>] [--ver <version>] [--tenant <tenant>]
FlagDescription
--uuid <worker-uuid>Worker to push. Defaults to the worker in the current directory (via geoengine.lock).
--ver <version>Version to push. Defaults to the highest numbered version available locally.
--tenant <tenant>Tenant to publish under. Defaults to your owned tenant.
Run from your worker directory without any flags to push the latest production version: 
geoengine push
GeoEngine will package the worker, upload the container image to the cloud registry, and register it in the selected workspace.

​
Step 3: Available to Your Team

After a successful push, team members will see the worker in their QGIS or ArcGIS Pro GeoEngine plugin and can run it through the cloud without installing anything locally.

​
Notes

  • Only production images (from geoengine apply without --dev) can be pushed. If you’ve only run geoengine apply --dev, run geoengine apply first.
  • If you have access to multiple tenants, use --tenant to target a specific one.
  • Use geoengine workers to see which versions have already been pushed (LATEST PUSHED column).