Semantic Workbench Setup Guide
October 8, 2024 · View on GitHub
This document covers the common setup information for the Semantic Workbench.
Codespaces
We recommend using GitHub Codespaces for developing with the Semantic Workbench. This will provide a pre-configured environment with all development tools already installed.
Local Development
Prerequisites
Recommended installers:
Development tools
The backend service for the Semantic Workbench is written in Python.
The frontend for the Semantic Workbench is written in Typescript.
The core dependencies you need to install are:
make- for scripting installation steps of the various projects within this repouv- for managing installed versions ofpython- for installing python dependenciesnvm- for managing installed versions ofnodepnpm- for installing node dependencies
Linux:
# make is installed by default on linux
sudo apt update && sudo apt install pipx
pipx ensurepath
pipx install uv
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.40.1/install.sh | bash
nvm install 20 lts
nvm use 20
npm install -g pnpm
macOS:
brew install make
brew install uv
brew install nvm
nvm install 20 lts
nvm use 20
npm install -g pnpm
Windows:
winget install ezwinports.make -e
winget install astral-sh.uv -e
winget install CoreyButler.NVMforWindows -e
On Windows, exit and restart the VSCode and/or terminal you installed from to re-load your environment variables and ensure the newly installed apps are available on your PATH.
Windows continued:
nvm install 20 lts
nvm use 20
npm install -g pnpm
If you haven't already, enable long file paths on Windows.
- Run
regedit. - Navigate to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem. - Find the
LongPathsEnabledkey. If it doesn’t exist, right-click on theFileSystemkey, selectNew > DWORD (32-bit) Value, and name itLongPathsEnabled. - Double-click on
LongPathsEnabled, set its value to1, and click OK.
Install and run the backend
See workbench-service/README.md