Using Statamic without Git integration

2 min read Updated 4 days ago

Using Statamic without Git integration

By default, Statamic applications are configured with Git integration to synchronize content changes back to your repository. However, you may want to disable this feature and manage all content directly on the server. This guide explains how to disable Git integration and configure additional persistent volumes for complete content persistence.

Why disable Git integration?

You might want to disable Git integration if:

  • You prefer managing all content through the control panel without version control

  • Multiple editors need to work simultaneously without dealing with Git conflicts

  • You want a simpler workflow without Git commits for every content change

  • Your content editors don't have Git knowledge or repository access

  • You're migrating from another CMS and want a traditional approach

Step 1: Disable Git integration

To disable Git integration for your Statamic application:

  1. Navigate to your application's settings page

  2. Go to the "Secrets" section

  3. Modify the following auto-mounted secrets:

    • Change STATAMIC_GIT_ENABLED from true to false

    • Change STATAMIC_GIT_AUTOMATIC from true to false

    • Change STATAMIC_GIT_PUSH from true to false

  4. Save your changes and redeploy the application

Step 2: Add persistent volumes for content

Without Git integration, you need to ensure all Statamic content directories are persisted. The default configuration only persists user uploads. Add these volume mounts to preserve all content:

  1. Navigate to your application's settings page

  2. Go to the "Volumes" section

  3. Add the following volume mounts:

    • /var/www/html/content - Stores all collections, entries, navigation, and taxonomies

    • /var/www/html/storage/forms - Already mounted by default for form submissions

    • /var/www/html/users - Stores user accounts and permissions

    • /var/www/html/resources/blueprints - Stores your content blueprints

    • /var/www/html/public/assets - Already mounted by default for uploads

Important considerations

What you lose without Git:

  • No version history for content changes

  • No ability to rollback to previous content versions

  • No code review process for content updates

  • Harder to maintain staging/production parity

  • Manual backup strategy required for content

What you gain:

  • Simpler workflow for content editors

  • No Git conflicts to resolve

  • Immediate content updates without commits

  • More traditional CMS experience

  • All changes persist automatically

Migration considerations

If you later decide to re-enable Git integration:

  • You'll need to manually commit all existing content to your repository

  • Ensure your local repository matches the server content before re-enabling

  • Consider the impact on other team members who may have outdated content

  • Test the synchronization in a staging environment first