Clean up: remove build-for-nas.sh, update deploy docs and push script
Build and Push Image / build (push) Has been cancelled
Build and Push Image / build (push) Has been cancelled
Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
+25
-8
@@ -137,6 +137,17 @@ Example: if your Gitea URL is `https://git.myserver.com` and your username is `j
|
||||
|
||||
---
|
||||
|
||||
## If you see “No matching online runner with label: ubuntu-latest”
|
||||
|
||||
Gitea **does not** provide hosted runners like GitHub. The workflow only runs if a **self-hosted runner** is registered with your Gitea instance and has the label `ubuntu-latest`.
|
||||
|
||||
**Options:**
|
||||
|
||||
1. **Use the manual build and push** (no runner needed): see **“If Gitea Actions aren’t available: manual push”** below. Run `./push-to-gitea.sh` from your PC after a one-time `podman login brassnet.ddns.net:33983`.
|
||||
2. **Set up a self-hosted runner**: in Gitea go to **Settings → Actions → Runners**, add a new runner on a machine that has Docker, and give it the label `ubuntu-latest` so the workflow can use it.
|
||||
|
||||
---
|
||||
|
||||
## Part 6: Use that image on your NAS
|
||||
|
||||
1. On the NAS, create a folder for the bot (e.g. `stoat-role-bot`) and put there:
|
||||
@@ -158,25 +169,31 @@ If your Gitea is only reachable on your LAN, the NAS must be able to reach that
|
||||
|
||||
---
|
||||
|
||||
## If Gitea Actions aren’t available: manual push
|
||||
## If Gitea Actions aren’t available (or “No matching runner”): manual push
|
||||
|
||||
You can build and push the image from your PC instead of using Actions:
|
||||
|
||||
1. Install Podman (or Docker) and log in to Gitea’s registry:
|
||||
1. **Allow HTTP registry** (if your Gitea is `http://`). One-time, on your PC:
|
||||
```bash
|
||||
podman login git.myserver.com
|
||||
mkdir -p ~/.config/containers
|
||||
printf '%s\n' '[[registry]]' 'location = "brassnet.ddns.net:33983"' 'insecure = true' > ~/.config/containers/registries.conf
|
||||
```
|
||||
(If you already have a `registries.conf`, add the `[[registry]]` block for `brassnet.ddns.net:33983` instead of overwriting.)
|
||||
|
||||
2. **Log in to the registry** (one-time per machine):
|
||||
```bash
|
||||
podman login brassnet.ddns.net:33983
|
||||
```
|
||||
Use your Gitea username and password (or token).
|
||||
|
||||
2. From the bot project folder:
|
||||
3. **Build and push** from the bot project folder:
|
||||
```bash
|
||||
export GITEA_REGISTRY=git.myserver.com
|
||||
export GITEA_OWNER=jorg
|
||||
cd "/path/to/Role Bot"
|
||||
./push-to-gitea.sh
|
||||
```
|
||||
Replace `git.myserver.com` and `jorg` with your Gitea host and username.
|
||||
Defaults are `brassnet.ddns.net:33983` and `Dawnsorrow`; the script lowercases the owner for the image name (e.g. `dawnsorrow/stoat-role-bot:latest`).
|
||||
|
||||
3. On the NAS, use the same image name as above and run the same `docker compose -f docker-compose.pull.yml` commands.
|
||||
4. On the NAS, use image **`brassnet.ddns.net:33983/dawnsorrow/stoat-role-bot:latest`** (lowercase `dawnsorrow`) and run the same `docker compose -f docker-compose.pull.yml` commands.
|
||||
|
||||
---
|
||||
|
||||
|
||||
Reference in New Issue
Block a user