Servebolt supports two primary workflows for using Git in your projects. You can use either the built-in Git integration within the Servebolt Admin Panel or work directly through the command line. Both approaches enable flexible deployment patterns tailored to your project’s needs.
Can I use CI tools?
Yes. Most CI providers work seamlessly because they rely on standard tools such as rsync, SSH, and symlinks. Node.js is also available on all Bolts for tooling purposes.
For teams working with WordPress, we also recommend Branch CI, a simple and developer-friendly deployment service that eliminates the need for complex configuration files. Branch includes a dedicated Servebolt recipe for quick integration.
Can I change the web server’s public/ folder?
Yes. When configuring Git in the Servebolt Admin Panel, you can choose which directory inside ~/site/public/ your deployment should target.
For example, you can deploy only to:
~/site/public/wp-content/~/site/public/wp-content/themes/your-theme/~/site/public/subfolder/- Or any other subdirectory within
~/site/public/
This allows for highly granular deployment workflows, such as pushing only theme files, plugin files, or compiled assets, without modifying the default server webroot or using symbolic links.
What happens when I click “Git deploy”?
When you click Git deploy, Servebolt pulls the files and folders from your configured Git branch into the specific target directory you selected within ~/site/public/.
- If your target is
~/site/public/, all repository files deploy to the webroot. - If your target is a subdirectory (e.g.,
~/site/public/wp-content/or~/site/public/subfolder/), only that directory receives the updated files.
New files are added, and existing files in the target directory are overwritten.
