Updated on: Fri Jun 20 11:59:37 PDT 2025
- Links
- Reference Guides
- VertiGIS Studio-Base: An
Introduction
- Why Use VertiGIS Studio-Base?
- System Requirements
- Preparation
- Deployment Overview
- On Windows: Install SSH and Supporting Tools
- On Remote: Setting up SSH
- On Remote: Remote in via SSH
- On Linux Host: Get the Package
- On Remote: Activate the Product
- On Linux Host: Initial Setup
- On Linux Host: Updating
- Check List
- This Release ( v1.1.714.249788-r15785867473-pr )
- Releases
- Images
- Repository
- Site
- Docker — Getting Started
- Docker Compose — Getting Started
- SSH Tutorial
- SSH Tutorial — Microsoft Learn
- SSH and VS Code
VertiGIS Studio-Base refers to the deployment of VertiGIS Studio using container technology, specifically Docker, on a Linux operating system. It provides a structured way to install and run VertiGIS Studio, which is designed for developing GIS applications that integrate with Esri’s ArcGIS Portal.
The setup involves preparing a Linux machine, obtaining necessary
account credentials for VertiGIS and GitHub (for image access), and
configuring the deployment using a docker-compose.yml file. The
package includes tools and scripts to aid in installation, activation,
and updates, such as install-tools.sh and activate.py.
Deploying VertiGIS Studio using the Studio-Base package offers several advantages focused on a managed and reproducible environment:
- Standardized Deployment: Utilizes Docker and Docker Compose for a consistent setup process across different Linux machines that meet the system requirements (specific Ubuntu or Debian distributions).
- Defined Operating Environment: Requires a specific Linux distribution, ensuring that the software runs in a known and tested environment.
- Integrated Ingress Management: The deployment package includes Traefik as an ingress proxy, demonstrating a method for managing external access to the Studio application.
- Configuration-Driven Setup: Key parameters such as the front-end
URL, VertiGIS Account ID, and ArcGIS Portal details are managed
through the
docker-compose.ymlfile, centralizing configuration. - Streamlined Installation and Activation: Provides scripts and a defined process for getting the necessary tools, activating the product, and starting the VertiGIS Studio services.
- Clear Update Path: Offers commands for pulling the latest images and updating the running deployment.
- ArcGIS Integration: The setup process explicitly includes steps for registering the application with an ArcGIS Portal, highlighting its core integration.
| Requirement | Spec |
|---|---|
| OS | Linux |
| Distribution | Ubuntu 24.04, Ubuntu 22.04, or Debian 12 (bookworm) |
| Memory | 4 GB Minimum, 8 GB Preferred |
| Disk | 16 GB Free |
In order to run VertiGIS Studio in containers, there are a few prerequisites that should be satisfied. Before you begin, please have the following at hand:
We require an appropriate license to run our software, but also, you will need registry credentials to pull down the software. Our support can help you with finding the following information:
- VertiGIS Account ID
- GitHub
- Account
- Permissions to ghcr.io/vertigis/studio/base
We require Linux to run VertiGIS Studio in containers. You must have a suitable distribution/version of Linux installed on an appropriately resourced machine. Please review the system requirements. We suggest using this Linux machine as a pure Docker host. In other words, do not install software directly on the host system.
The front-end URL for the software’s hosting location is a required configuration. Multiple internal components utilize this value for proper functionality.
Go to your portal and create a web application:
- Register this application (enable OAUTH2).
- Provide a Redirect URL (use the Front-End URL).
- Note the App ID.
The primary part of the installation occurs on the Linux machine you have provisioned for this task. You can use Windows as a means to remotely administer your Linux system.
The package includes an ingress proxy (Traefik) and demonstrates how to use the ingress mechanism. If you are using Windows, we suggest enabling ACME on your Enterprise CA as this will be the easiest way to acquire Web Server certificates through the ingress proxy.
If using Windows to remotely administer your Linux environments, you will need a variety of tools. We suggest using a full-featured SSH client like VS Code to perform administrative tasks. VS Code supports remote file editing as well as remote command execution.
# If not already done, install supporting tools
> Get-WindowsCapability -Online -Name RSAT.ActiveDirectory.* | Add-WindowsCapability -Online
> Add-WindowsCapability -Online -Name OpenSSH.Client
# If desired, install vscode
> winget install vscode
> code --install-extension ms-vscode-remote.remote-sshYou can do this via the GUI as well:
- Goto Windows Optional Features -> Add an Optional Feature:
- Install RSAT: Active Directory Domain Services
- Install OpenSSH Client
- Optionally, download and install the following:
- VS Code
- Install the Remote SSH Extension
# Create SSH key (we suggest using the defaults):
# NOTE: Only do this once or if you want to generate new key.
> ssh-keygen -t ed25519
# Register for passwordless login (optional but recommended)
# If on Linux:
> ssh-copy-id user@host
# If on Windows, you'll need to do this manually:
> scp %USERPROFILE%\.ssh\id_ed25519.pub user@host:~
> ssh user@host
> umask 077
> mkdir -p .ssh
> read line < id_ed25519.pub
> echo $line >> .ssh/authorized_keys
> rm id_ed25519.pub
> exit# If using ssh directly:
> ssh user@host
# If using vscode:
> code --remote ssh-remote+user@host /home/user# If desired, use curl:
> mkdir -p ~/deploy-studio
> cd ~/deploy-studio
> curl -fsSL https://github.com/vertigis/studio-base-internal/archive/refs/tags/v1.1.714.249788-r15785867473-pr.tar.gz | tar -xz
# If desired, use git:
> git clone --depth 1 --branch v1.1.714.249788-r15785867473-pr https://github.com/vertigis/studio-base-internal ~/deploy-studio
> cd ~/deploy-studio
# Install Docker and supporting tools if needed
> sudo ./install-tools.sh
> exec sudo su - $USER# If session is local xterm, local vscode, or remote vscode:
> ~/deploy-studio/activate.py
# If session is remote through ssh:
> ssh -L localhost:7780:localhost:7780 user@host ~/deploy-studio/activate.py# Switch to the deployment folder
> cd ~/deploy-studio
# If you need to discover your Enterprise Root certificates
> ./extract-ca-certs.py
# Edit configuration for VertiGIS Studio
# See checklist for what to edit.
# If using a plain terminal, try one of these:
> nano docker-compose.yml
> vi docker-compose.yml
# If using a GUI, try one of these:
> code docker-compose.yml &
> gedit docker-compose.yml &
> kate docker-compose.yml &
> mousepad docker-compose.yml &
# Gain access to images
> gh auth login -w -s repo,read:packages
> gh auth token | docker login ghcr.io -u x-access-token --password-stdin
# Pull/Start VertiGIS Studio
> docker compose up --wait --build
# Optionally, deploy the VertiGIS Studio Printing Engine
> docker exec vs-studio-main-1 util-deploy-printing-engine# Switch to the deployment folder
> cd ~/deploy-studio
# If login has expired, gain access to images
> gh auth login -w -s repo,read:packages
> gh auth token | docker login ghcr.io -u x-access-token --password-stdin
# Optionally, pull down VertiGIS Studio
> docker compose pull
# Then, upgrade VertiGIS Studio
> docker compose up --wait --build
# Optionally, hot refresh configuration
> docker exec vs-studio-main-1 util-refresh- Editing docker.compose.yml:
- Set the front-end URL via
FRONTEND_URL - Set the VertiGIS Account ID via
VERTIGIS_ACCOUNT_ID - Set the ArcGIS Portal URL via
ARCGIS_PORTAL_URL - Set the ArcGIS App ID via
ARCGIS_APP_ID
- Set the front-end URL via