Setup

Setup

1. Install Docker Desktop
2. Install Git
3. Install .NET 9 SDK
4. Clone daps (currently on Codeberg)
5. Copy daps.yaml.example to daps.yaml — this is your personal config file and is gitignored
6. Set up the dapsman command (instructions below)
7. Set up a project (instructions below)

Setting up the dapsman command

Add <repo>/bin to your PATH once after cloning. The bin/ folder contains launcher scripts for each platform that delegate to dotnet run, so you always run from source without a separate build step.

Windows — add C:\path\to\daps\bin to your user PATH via System Properties, or for the current session:

$env:PATH += ";C:\path\to\daps\bin"

Mac/Linux — make the script executable, then add to PATH:

chmod +x /path/to/daps/bin/dapsman
export PATH="/path/to/daps/bin:$PATH"  # add to ~/.zshrc or ~/.bashrc to persist

After that, dapsman works from any directory.

Initializing a project from a template

Daps has 2 templates currently, Wordpress (daps/templates/wordpress) and Grist (daps/templates/grist) — note both have readmes as well, worth looking at.

In this example I’ll create the Wordpress site at wp.dapster.org. Assume that the setup steps above have been completed and Daps is cloned at C:\repos\daps.

1. run init: dapsman init --template wordpress --name dapster-wp --prod-url https://mywebsite.com
   • This creates a folder at C:\repos\dapster-wp
   • it also replaces placeholder values in Caddy and Docker files for the project name and production URLs.
   • see below for next steps if you omit the --prod-url switch
2. run local build: dapsman local build
   • dapsman will try to update your local hosts file to add this entry, but if you’re not running as administrator you will need to do it manually: 127.0.0.1 dapster-wp.localhost
   • you may need to run dapsman local caddy restart depending on whether you’re adding a project to an existing setup
3. visit https://dapster-wp.localhost and set up your local Wordpress installation (e.g. themes, plugins, posts, etc.)

For production, see Deployment.

Omitting the —prod-url switch

If you run init without specifying the production URL, you’ll need to edit some files manually:

1. edit caddy site files
   • Open C\repos\dapster-wp\_caddy_sites\dapster-wp.prod.caddy and dapster-wp.offline.caddy
   • replace text of dapster-wp.example.com with the actual domain, e.g. wp.dapster.org
2. edit docker files
   • Open C\repos\dapster-wp\_docker\compose_dapster-wp.prod.yaml
   • set WP_HOME and WP_SITEURL URLs to https://wp.dapster.org

Initializing a project without a template

TODO