-
Notifications
You must be signed in to change notification settings - Fork 4
Getting started
This guide walks you through the shortest path from installation to a working local Govard project.
Navigate to your project root and run:
cd /path/to/your/project
govard initGovard inspects composer.json or package.json, detects the framework, and writes .govard.yml.
| Framework | Detection |
|---|---|
| Magento 2 |
composer.json with magento/magento2-base
|
| Magento 1 / OpenMage |
composer.json patterns |
| Laravel |
artisan file + composer.json
|
| Next.js |
package.json with next dependency |
| Emdash | Emdash project markers |
| Drupal |
composer.json with drupal/core
|
| Symfony | symfony/framework-bundle |
| Shopware | shopware/core |
| CakePHP | cakephp/cakephp |
| WordPress |
wp-config.php or wp-login.php
|
| Custom | Interactive stack picker (govard init --framework custom) |
govard init --framework magento2
govard init --framework customIf you are transitioning from Warden or DDEV, Govard can automatically detect your setup and seamlessly copy your local database volume so you don't lose any data:
govard init --migrate-from warden
govard init --migrate-from ddevgovard env upThis renders a per-project compose file under ~/.govard/compose/ and starts your specialized stack.
govard up --quickstart # Alias: govard env up
govard env up --pull # Pull latest images first
govard env up --fallback-local-build # Build images locally if pull fails- Detect framework context
- Validate config, Docker, ports, and prerequisites
- Render compose file into
~/.govard/compose/ - Start containers in detached mode
- Verify proxy and host wiring
| Shortcut | Equivalent |
|---|---|
govard up |
govard env up |
govard down |
govard env down |
govard restart |
govard env restart |
govard ps |
govard env ps |
govard logs |
govard env logs |
Auto-inject container settings into app/etc/env.php:
govard config autogovard config get php_version
govard config get stack.db_typegovard shell-
PHP frameworks (Magento, Laravel, etc.): opens the
phpcontainer at/var/www/html -
Node-first frameworks (Next.js, Emdash): opens the
webcontainer at/app
Govard routes project domains through the shared Caddy proxy:
| Target | Command |
|---|---|
| App URL |
https://<project>.test in browser |
| Admin panel | govard open admin |
| Mail (Mailpit) | govard open mail |
| Database (PHPMyAdmin) | govard open db |
| Database client URL | govard open db --client |
# Start work
govard up
# Follow logs
govard logs php -f
# Toggle Xdebug
govard debug on
# Enter shell
govard shell
# Stop work
govard downTo clone an existing environment from a remote server:
govard bootstrap --clone -e staging --no-pii --no-noiseFor a fresh framework installation:
govard bootstrap --framework magento2 --fresh --framework-version 2.4.9
govard env up
govard open admingovard doctor
govard doctor trust # Fix browser SSL warningsIf your browser shows HTTPS trust warnings after setup, run govard doctor trust to re-import the Root CA.
| Topic | Link |
|---|---|
| All CLI commands | CLI Commands |
| Configuration options | Configuration |
| Framework-specific notes | Frameworks |
| SSL and DNS setup | SSL and Domains |
| Remote environments | Remotes and Sync |
| Desktop app | Desktop App |
Govard — Go-based Versatile Runtime & Development GitHub · Releases · Issues · MIT License