A lightweight desktop application for managing PHP Deployer deployments across multiple projects.
Register your projects, see their environments, deploy with a click, and track release history — all from one interface.
- Manage deployments for multiple projects from a single app
- Auto-discovers environments from each project's
hosts.yaml - Optional per-environment links from
hosts.yamlshown on deployment cards - Quick deploy with tag or branch selection
- Fetch remote git tags and branches to refresh deploy targets
- View deployment output after completion
- Release history per environment
- Light and dark theme
- Cross-platform: Linux (primary), macOS (planned)
- PHP Deployer (
dep) installed and available in PATH - Git installed (for tag/branch discovery)
Download the latest release from the Releases page.
- Linux:
.debpackage or standalone binary
See CONTRIBUTING.md for build instructions.
Each project you want to manage needs a .deployments/ directory containing:
deploy.php— Your PHP Deployer recipehosts.yaml— Host configuration defining your environments
Click "+ Add Project" in the sidebar and enter the absolute path to your project root (the directory containing .deployments/).
- Select your project in the sidebar
- Click "Deploy" on the environment you want to deploy to
- Select a tag or branch
- Hit Deploy
The deployment output appears after the process completes.
The app reads your existing PHP Deployer hosts configuration. Both formats are supported:
hosts:
prod:
hostname: server.example.com
remote_user: deploy
deploy_path: /var/www/app
branch: master
keep_releases: 5
stage: prod
links:
- { weburl: https://classe.scolavisa.eu }
staging:
hostname: server.example.com
remote_user: deploy
deploy_path: /var/www/staging
branch: develop
keep_releases: 3
stage: staging| Field | Required | Description |
|---|---|---|
hostname |
yes | Server hostname or IP |
remote_user |
yes | SSH user for deployment |
deploy_path |
yes | Remote path for deployments |
branch |
no | Default branch for this environment |
stage |
no | Stage identifier (e.g., "prod", "staging") |
keep_releases |
no | Number of recent releases to show in the app (default: 5) |
links |
no | Optional list of { weburl: ... } entries shown as clickable URLs on the environment card |
Under the hood, the app executes these dep commands:
# Deploy
dep deploy -f .deployments/deploy.php <environment>
dep deploy -f .deployments/deploy.php <environment> --tag=<tag>
dep deploy -f .deployments/deploy.php <environment> --branch=<branch>
# Fetch release history
dep -f .deployments/deploy.php releases <environment>| What | Where (Linux) |
|---|---|
| Registered projects | ~/.config/deployment-manager/config.json |
| Logs | ~/.local/share/com.deployment-manager.app/logs/ |
| UI preferences (theme) | WebView localStorage in ~/.local/share/com.deployment-manager.app/ |
On macOS, config is stored in ~/Library/Application Support/deployment-manager/config.json.
- Theme: Click the ☀/🌙 button in the bottom-right corner to switch between light and dark mode
- Projects: Listed alphabetically in the sidebar with capitalized names
- Fetch git: Use Fetch git on the project panel to run
git fetch --all --tagsso new remote branches and tags appear in the deploy dropdowns - Links: Add optional
linksentries under a host inhosts.yamlto show the target URL(s) on that environment's card - Release history: Shows the most recent releases based on
keep_releasesin your hosts.yaml (defaults to 5) - Environments: Displayed in alphabetical order for consistency across sessions
- Logs: Check the log directory if something isn't working — environment discovery and deployment errors are logged there
MIT — see LICENCE