Synaro docs
Projects
Lifecycle, metadata, imports, sharing, and how projects map to services.
A project is the top-level unit in Synaro. It stores name, slug, description, optional Git remote URL, Docker base image selection, and environment status synchronized from the environment service.
Creation flows
- Blank / prompt — AI-assisted scaffold with chosen runtime image (Node, Python, Go, Nginx, Ubuntu, or automatic detection)
- GitHub import — clone repository into the workspace volume on provision
- Folder upload — import files without Git history (no commit metadata in the file tree)
Collaboration
Project owners can invite members via share links (project invites with expiring tokens). Members get workspace access; owners retain delete and invite management.
Data stores
Project metadata lives in the main app database (Prisma on PostgreSQL). The project-service maintains its own schema for service-specific records. Environment runtime state is stored separately in the environment-service database.