More fixing of things.

Signed-off-by: copilotcoder <copilotcoder@darkhelm.org>
This commit is contained in:
copilotcoder
2026-05-20 17:21:12 -04:00
parent 212b377147
commit c669e1225b
3 changed files with 21 additions and 4 deletions

View File

@@ -29,13 +29,13 @@ jobs:
mkdir -p ~/.ssh
echo "${SSH_PRIVATE_KEY}" > ~/.ssh/id_rsa
chmod 600 ~/.ssh/id_rsa
ssh-keyscan -p 2222 dogar.darkhelm.org >> ~/.ssh/known_hosts 2>/dev/null
ssh-keyscan -p 2222 kankali.darkhelm.lan >> ~/.ssh/known_hosts 2>/dev/null
fi
# Clone repository
GIT_SSH_COMMAND="ssh -o StrictHostKeyChecking=no" \
git clone --depth 1 \
ssh://git@dogar.darkhelm.org:2222/DarkHelm.org/plex-playlist.git .
ssh://git@kankali.darkhelm.lan:2222/DarkHelm.org/plex-playlist.git .
# Clean up SSH key
rm -f ~/.ssh/id_rsa

View File

@@ -131,6 +131,23 @@ Each runner supports multiple Docker environments:
- `node-latest``node:20-bookworm-slim`
- `ubuntu-act``catthehacker/ubuntu:act-latest`
### Mirroring the `ubuntu-act` Runner Image
If GHCR pulls are flaky, mirror the runner image into your local registry and point the label at that mirror instead of the upstream tag.
Example mirror flow:
```bash
docker pull ghcr.io/catthehacker/ubuntu:act-latest
docker tag ghcr.io/catthehacker/ubuntu:act-latest kankali.darkhelm.lan:3001/darkhelm.org/act-ubuntu:act-latest
docker push kankali.darkhelm.lan:3001/darkhelm.org/act-ubuntu:act-latest
```
Recommended runner label once mirrored:
```bash
GITEA_RUNNER_LABELS=ubuntu-latest:docker://ubuntu:22.04,node-latest:docker://node:20-bookworm-slim,python-latest:docker://python:3.14-slim,ubuntu-act:docker://kankali.darkhelm.lan:3001/darkhelm.org/act-ubuntu:act-latest
```
If you want a failover strategy, keep the cached image tagged in the local registry and only refresh it when the upstream digest changes. That way the runner never depends on GHCR at job start.
### Workflow Design
Multi-stage pipeline with artifact passing:
1. **Setup**: Checkout code, create artifacts

View File

@@ -24,7 +24,7 @@ Renovate is an automated dependency update tool that creates pull requests to ke
### Option 2: Self-Hosted (For Gitea/Custom Git Servers)
Since your project uses `dogar.darkhelm.org` (Gitea), you'll need to run Renovate as a service:
Since your project uses `kankali.darkhelm.lan` (Gitea), you'll need to run Renovate as a service:
#### Docker-based Self-Hosted Setup
@@ -46,7 +46,7 @@ mkdir -p ~/.config/renovate
# ~/.config/renovate/config.js
module.exports = {
platform: 'gitea',
endpoint: 'https://dogar.darkhelm.org/api/v1',
endpoint: 'https://kankali.darkhelm.lan/api/v1',
token: process.env.RENOVATE_TOKEN,
gitAuthor: 'Renovate Bot <renovate@darkhelm.org>',
repositories: ['DarkHelm.org/plex-playlist'],