Automatic Git deployments made simple. SPDeploy monitors your Git repositories and automatically pulls changes to your servers - no complex CI/CD setup required. Perfect for developers who want instant deployments without the overhead.
✨ Zero configuration • 🚀 Single binary • 🔒 SSH-based • 📦 Any Git provider • ⚡ Lightweight
# 1. Download from GitHub releases page
# Visit: https://github.com/simonjcarr/spdeploy/releases/latest
# Download the binary for your platform and extract
# 2. Add your repository
spdeploy add [email protected]:username/myapp.git /var/www/myapp
# 3. Start monitoring
spdeploy runThat's it! SPDeploy now watches your repository and auto-deploys on every push.
- Universal Git Support - Works with GitHub, GitLab, BitBucket, and any Git server with SSH
- Simple as It Gets - No YAML configs, no pipelines, no complexity
- Deploy Scripts - Automatically runs
spdeploy.shafter pulling (build, restart services, etc.) - Multiple Repositories - Monitor unlimited repos from different providers simultaneously
- Branch Control - Deploy from any branch (main, develop, staging, etc.)
- Lightweight - Single 10MB binary, uses < 20MB RAM
- Cross-Platform - Linux, macOS, Windows, ARM/AMD64
- Background Service - Runs as a daemon, survives reboots
- Real-time Logs - Monitor deployments as they happen
Download the appropriate binary for your platform from the GitHub releases page.
# Option 1: Download via command line (replace with your platform)
# Linux AMD64
curl -L https://github.com/simonjcarr/spdeploy/releases/latest/download/spdeploy-linux-amd64.tar.gz | tar -xz
sudo mv spdeploy /usr/local/bin/
# Linux ARM64
curl -L https://github.com/simonjcarr/spdeploy/releases/latest/download/spdeploy-linux-arm64.tar.gz | tar -xz
sudo mv spdeploy /usr/local/bin/
# macOS (Intel)
curl -L https://github.com/simonjcarr/spdeploy/releases/latest/download/spdeploy-darwin-amd64.tar.gz | tar -xz
sudo mv spdeploy /usr/local/bin/
# macOS (Apple Silicon)
curl -L https://github.com/simonjcarr/spdeploy/releases/latest/download/spdeploy-darwin-arm64.tar.gz | tar -xz
sudo mv spdeploy /usr/local/bin/
# Option 2: Manual download
# 1. Go to https://github.com/simonjcarr/spdeploy/releases/latest
# 2. Download the .tar.gz file for your platform
# 3. Extract and install:
tar -xzf spdeploy-*.tar.gz
chmod +x spdeploy
sudo mv spdeploy /usr/local/bin/- Visit the releases page
- Download the Windows ZIP file for your architecture (amd64)
- Extract the ZIP file
- Add the directory to your PATH environment variable
SPDeploy uses SSH keys for secure authentication. If you don't have SSH access set up:
# Generate SSH key (if needed)
ssh-keygen -t ed25519 -C "spdeploy@server"
# Copy public key to clipboard
cat ~/.ssh/id_ed25519.pub
# Add to your Git provider:
# GitHub: Settings → SSH Keys → New SSH key
# GitLab: Settings → SSH Keys → Add key
# BitBucket: Personal settings → SSH keys → Add key
# Test connection
ssh -T [email protected]# Add a repository
spdeploy add <ssh-url> <deploy-path> [options]
--branch <name> # Branch to monitor (default: main)
--script <path> # Custom deploy script
# Examples
spdeploy add [email protected]:team/webapp.git /var/www/webapp
spdeploy add [email protected]:api/v2.git /opt/api --branch develop
spdeploy add [email protected]:company/app.git ~/app --script deploy.sh
# Start/stop monitoring
spdeploy run # Start in foreground
spdeploy run -d # Start as daemon (background)
spdeploy stop # Stop daemon
spdeploy status # Check if daemon is running
# View repositories
spdeploy list
# Remove repository
spdeploy remove <ssh-url>
# View logs
spdeploy log # Show all logs
spdeploy log -f # Follow logs (real-time)Create a deploy script in your repository that runs automatically after each pull. By default, SPDeploy looks for spdeploy.sh in your repository root, but you can specify a custom script path using the --script flag.
Important: The script is executed from the repository's root directory, not from the directory where the script is located. All relative paths in your script will be relative to the repository root.
#!/bin/bash
# spdeploy.sh - Runs automatically after pulling changes
# Working directory: repository root
# Node.js example
npm ci --production
npm run build
pm2 restart app
# Python example
pip install -r requirements.txt
systemctl restart myapp
# Docker example
docker-compose down
docker-compose up -d --buildIf your script is in a subdirectory and needs to reference files relative to its location:
#!/bin/bash
# scripts/deploy.sh - Script in subdirectory
SCRIPT_DIR="$(cd "$(dirname "$0")" && pwd)"
# Files created here will be in the repository root
echo "Deployed at $(date)" > deploy.log
# To create files in the script's directory
echo "Deployed at $(date)" > "$SCRIPT_DIR/deploy.log"Make it executable:
chmod +x spdeploy.sh
git add spdeploy.sh
git commit -m "Add deploy script"
git pushLinux (systemd)
# Create service file
sudo tee /etc/systemd/system/spdeploy.service > /dev/null << EOF
[Unit]
Description=SPDeploy Git Auto-Deploy
After=network.target
[Service]
Type=simple
User=$USER
ExecStart=/usr/local/bin/spdeploy run
Restart=always
RestartSec=10
[Install]
WantedBy=multi-user.target
EOF
# Enable and start
sudo systemctl daemon-reload
sudo systemctl enable spdeploy
sudo systemctl start spdeploymacOS (launchd)
# Create plist file
sudo tee ~/Library/LaunchAgents/io.spdeploy.plist > /dev/null << EOF
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Label</key>
<string>io.spdeploy</string>
<key>ProgramArguments</key>
<array>
<string>/usr/local/bin/spdeploy</string>
<string>run</string>
</array>
<key>RunAtLoad</key>
<true/>
<key>KeepAlive</key>
<true/>
</dict>
</plist>
EOF
# Load service
launchctl load ~/Library/LaunchAgents/io.spdeploy.plistMonitor different projects from various Git providers:
# Frontend from GitHub
spdeploy add [email protected]:company/frontend.git /var/www/frontend
# API from GitLab
spdeploy add [email protected]:backend/api.git /var/www/api --branch production
# Microservice from BitBucket
spdeploy add [email protected]:team/service.git /opt/service --branch develop
# Start monitoring all
spdeploy run -dDeploy different branches to different locations:
# Production
spdeploy add [email protected]:app/website.git /var/www/prod --branch main
# Staging
spdeploy add [email protected]:app/website.git /var/www/staging --branch staging
# Development
spdeploy add [email protected]:app/website.git /var/www/dev --branch developUse different scripts for different deployments:
# Production with extensive checks
spdeploy add [email protected]:app/api.git /opt/api \
--branch main \
--script scripts/deploy-production.sh
# Staging with quick deploy
spdeploy add [email protected]:app/api.git /opt/api-staging \
--branch staging \
--script scripts/deploy-staging.shSPDeploy works great with Docker:
# spdeploy.sh in your repo
#!/bin/bash
docker-compose pull
docker-compose up -d --remove-orphans
docker image prune -fSPDeploy works with any Git server that supports SSH:
# Self-hosted GitLab
spdeploy add [email protected]:internal/app.git /var/www/app
# Gitea
spdeploy add [email protected]:team/project.git /opt/project
# GitHub Enterprise
spdeploy add [email protected]:org/repo.git /var/www/repoSPDeploy stores its configuration in:
- Linux/macOS:
~/.spdeploy/config.json - Windows:
%USERPROFILE%\.spdeploy\config.json
You can edit this file directly if needed, but using CLI commands is recommended.
# Check if SPDeploy is running
ps aux | grep spdeploy
# View logs for errors
spdeploy log -f
# Test SSH connection
ssh -T [email protected]
# Manually test repository access
git ls-remote [email protected]:username/repo.git# Ensure SSH key has correct permissions
chmod 600 ~/.ssh/id_ed25519
chmod 644 ~/.ssh/id_ed25519.pub
# Add SSH key to agent
ssh-add ~/.ssh/id_ed25519
# Check repository path permissions
ls -la /var/www/myapp# Check script is executable
ls -la spdeploy.sh # Should show -rwxr-xr-x
# Make executable
chmod +x spdeploy.sh
# Test script manually
cd /var/www/myapp && ./spdeploy.sh- CPU: Minimal usage, polls every 60 seconds
- Memory: < 20MB RAM per instance
- Disk: 10MB binary + your repository sizes
- Network: Only active during git pull operations
- Use deploy keys instead of personal SSH keys
- Restrict repository access to read-only where possible
- Run as non-root user for better security
- Use separate SSH keys for different environments
- Monitor logs regularly for unexpected activity
- Keep SPDeploy updated for security patches
# Clone repository
git clone https://github.com/simonjcarr/spdeploy.git
cd spdeploy
# Build
go build -o spdeploy cmd/spdeploy/main.go
# Install
sudo mv spdeploy /usr/local/bin/Contributions are welcome! Please feel free to submit a Pull Request.
MIT License - see LICENSE file for details.
- Issues: GitHub Issues
- Discussions: GitHub Discussions
- Email: [email protected]
Made with ❤️ by developers, for developers. Because deployment should be simple.