Skip to main content
Use this page to get a StacyVM server running before you follow the quickstart.

Prerequisites

  • Linux is recommended for runtime work. macOS is useful for SDK and docs development, but Docker provider behavior should be certified on Linux before public claims.
  • Docker is required for the default local provider path.
  • Go is required only when building from source.
See Prerequisites for the full local, SDK, and production checklist.

OS-Specific Setup

Use the Prerequisites OS setup before choosing an installation mode:
  • macOS: Docker Desktop plus Go for make serve.
  • Windows: WSL 2 with Ubuntu and Docker Desktop WSL integration.
  • Linux: Docker and Go from your distribution package manager.
  • Ubuntu: Docker Engine, Compose plugin, Go, Git, curl, and make.
For individual local development from a source checkout, use the one-command setup:
This checks the host, builds StacyVM, and starts the API server. You can also use the npm/npx bootstrapper:
That command can clone the repo, install Node package dependencies, download Go modules, build StacyVM, and start the server. It does not install Docker Desktop or Go for you.

Option 1: Release Binary

Use a signed GitHub release for production-like installs.
Validate the release artifacts before you install them in production:
Replace v0.14.4 with the release tag you plan to deploy.

Option 2: Docker Compose

The repository includes a production-oriented Docker Compose starting point.
Edit .env before exposing the service. Use strong API keys, exact CORS origins, and a persistent data directory.

Option 3: Source Checkout

Build from source when you are contributing to StacyVM itself.

Configure Auth

For local experiments you can run without auth. For any shared host, enable auth and pass X-API-Key from clients.

Verify The Host

Run config validation before a deploy:
Run live host diagnostics after the service is installed:

Continue

Once the server responds, follow the quickstart. If setup fails, use the troubleshooting guide.