bound volumes are gone

docker-registry/.gitignore

@@ -0,0 +1 @@
+data

gitea/README.md

@@ -10,9 +10,9 @@ docker build -t cerc/act-runner:local .
 ```
 
 #### Deploy Gitea Stack
-1. `cd ./gitea`
+1. `cd ../act-runner`
 1. Build the task executor container: `docker build -t cerc/act-runner-task-executor:local -f Dockerfile.task-executor .`
-1. Run the script `./run-this-first.sh`
+1. `cd ../gitea`
 1. Bring up the gitea cluster `docker compose up -d`
 1. Run the script `./initialize-gitea.sh`
 1. Note the access token printed, it will be needed to publish packages.
@@ -29,4 +29,4 @@ Details on how to setup remote debugging of the gitea server inside its containe
 #### Action Runners
 
 A Dockerized action runner is deployed by default for the labels `ubuntu-latest` and `ubuntu-22.04`.  Details on deploying
-additional runners can be found [here](../act-runner/act-runner.md).
+additional runners can be found [here](act-runner.md).

gitea/act-runner.md

@@ -11,7 +11,7 @@ The following example uses `gitea/act_runner` 0.2.6 to deploy a runner on macOS
 
 > Note: Runners can be registered globally for an entire Gitea instance, for a specific organization, or for a single repo.  This example registers globally.
 
-Before executing the runner, first obtain a registration token by visiting http://gitea.local:3000/admin/actions/runners, clicking the 'Create new Runner' button, and copying the displayed
+Before executing the runner, first obtain a registration token by visiting [/admin/actions/runners](http://gitea.local:3000/admin/actions/runners), clicking the 'Create new Runner' button, and copying the displayed
 registration token, for example, `FTyMBkcK9ErmD0wm8LfBzfXOUUlQA7dBJF6BB64Z`.
 
 ### Runner Registration and Startup

gitea/run-this-first.sh

@@ -1,7 +0,0 @@
-#!/usr/bin/env bash
-if [[ -n "$CERC_SCRIPT_DEBUG" ]]; then
-    set -x
-fi
-mkdir -p ./gitea
-mkdir -p ./gitea/ssh
-mkdir -p ./act-runner