Enterprise deployment runbook¶

Deploy Strixonomy (VS Code) and Strixonomy (CLI/LSP) in regulated, air-gapped, or centrally managed environments. Complements enterprise evaluation and production readiness.

Deployment patterns¶

Ontology content stays on disk — no cloud upload by default (security policy).

VS Code extension rollout¶

Option A — Marketplace or Open VSX (internet-connected)¶

1. Allowlist extension publisher strixonomy and extension strixonomy.strixonomy
2. Cursor / Open VSX clients: allowlist open-vsx.org/extension/strixonomy/strixonomy (v0.11.0+)
3. Pin minimum VS Code 1.85+ (vscode-install)
4. Document conditional Trust workspace policy: bundled LSP works in Restricted Mode; Trust only for custom lspPath / robotPath (vscode-install)
5. Communicate multi-root behavior — all folders are indexed since v0.10 (FAQ)

Option B — Offline / air-gapped (recommended for regulated envs)¶

1. On a connected staging machine, download from GitHub Releases for version v0.27.0 (or your pinned version):
2. strixonomy-v0.27.0.vsix (pattern: strixonomy-v<version>.vsix)
3. SHA256SUMS
4. NOTICES
5. Optional: strixonomy-lsp-v<version>-<platform>.tar.gz per platform if not using bundled VSIX LSP
6. Verify checksums:

sha256sum -c SHA256SUMS

1. Transfer artifacts to internal artifact store (Artifactory, Nexus, S3 with policy, etc.)
2. Distribute install procedure to developers:

Extensions → … → Install from VSIX… → select internal copy of strixonomy-*.vsix

1. Archive NOTICES and version metadata alongside the VSIX for legal/compliance audits.

See release integrity for full verification steps.

Option C — Build from source (highest control)¶

From an internal git mirror of the repository:

./scripts/package-extension.sh
cd extension && npx vsce package --no-dependencies

Install resulting VSIX internally. Requires Rust + Node toolchains on build host.

Pinning and updates¶

Pre-1.0: expect minor release API changes — test CI and integrators before org-wide bump.

CLI on CI agents¶

Linux x64 (recommended)¶

Download pinned release binary — fastest cold start:

VERSION=0.27.0
ASSET="strixonomy-v${VERSION}-x86_64-unknown-linux-gnu.tar.gz"
BIN="strixonomy-v${VERSION}-x86_64-unknown-linux-gnu"
curl -fsSL -o "${ASSET}" \
  "https://github.com/eddiethedean/strixonomy/releases/download/v${VERSION}/${ASSET}"
tar xzf "${ASSET}"
chmod +x "${BIN}"
./"${BIN}" validate /path/to/ontologies

Verify against SHA256SUMS in production pipelines (ci-integration).

macOS / Windows CI¶

Cache ~/.cargo or an internal cargo registry mirror to reduce cargo install time.

Language server hardening¶

Group policy / MDM checklist¶

• [ ] Extension allowlist includes strixonomy.strixonomy OR distribute VSIX via internal portal only
• [ ] Block Marketplace auto-update if policy requires pinned VSIX
• [ ] Document single-root workspace convention in internal wiki
• [ ] Provide internal support link for troubleshooting (empty explorer, LSP start failures)
• [ ] Archive NOTICES + version per deployment wave (LGPL compliance)

Remote development (SSH, dev containers, Codespaces)¶

Documentation does not certify these environments. Pilot checklist:

1. Install VSIX on remote VS Code server if using Remote-SSH (extension runs remotely)
2. Confirm bundled strixonomy-lsp matches remote OS/architecture (VSIX bundles Linux/macOS/Windows x64)
3. Open ontology folder on remote filesystem (indexing is local to LSP process)
4. Re-run first success on the remote host

Report gaps via GitHub issues.

Audit and logging¶

Strixonomy does not ship centralized audit logging. For compliance:

Reference architecture¶

flowchart LR
  subgraph corp [Corporate network]
    Artifactory[Internal artifact mirror]
    Dev[Developer VS Code]
    CI[CI runner Linux x64]
    Ontology[Ontology project]
  end
  Artifactory -->|VSIX NOTICES CLI| Dev
  Artifactory -->|strixonomy binary| CI
  Dev -->|stdio| LSP[strixonomy-lsp]
  LSP --> Ontology
  CI --> Ontology

Related¶

• Release integrity
• CI integration
• Production readiness
• Performance and sizing
• Install VS Code