Start with gcms
Start with gcms
Trying, deploying or integrating gcms? Here are the shortest paths: official site, releases, one-line install and deployment notes.
If you're evaluating gcms, the best next step is to run it. It needs no separate database service and no frontend build chain; the downloaded package is already a standard runtime directory.
Try it quickly
- Official site: ccvar.com
- Downloads: GitHub Releases
- One-line install:
curl -fsSL https://raw.githubusercontent.com/ccvar/gcms-releases/main/install.sh | sh
Environment requirements
gcms is not a heavy platform. A small server is enough to launch a product site, docs hub or resource directory before you scale up.
- CPU: 1 vCPU is enough to start and handle normal publishing work;
- Memory: a 512MB VPS can deploy a regular product site, docs site or resource directory;
- Disk: the package is small; most growth comes from the SQLite database, uploads and logs;
- OS: Linux, macOS and Windows packages are available for amd64 / arm64;
- Public entry: in production, put Caddy on 80/443 and bind gcms to
127.0.0.1:8080.
When content volume or traffic grows, increase memory and disk based on real usage.
Deployment suggestion
In production, bind gcms to 127.0.0.1:8080 and put Caddy in front for HTTPS, compression and HTTP/3. The release repository also includes standalone Caddy install and configuration scripts.
Report an issue
When reporting installation, update or deployment issues, include your platform, gcms version, log snippets and steps to reproduce. The more complete the context, the faster the fix.