efforting.tech/gitea.efforting.tech
1
0
Fork 1
Code Issues 10 Pull Requests Actions Packages Projects Releases Wiki Activity

Update planning/automated-tasks.md

Browse Source
This commit is contained in:
Mikael Lövqvist
2026-05-10 16:36:29 +00:00
parent 5043a48337
commit 880d0d40f2
1 changed files with 9 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
planning/automated-tasks.md
View File

@@ -12,4 +12,12 @@ One thing not yet addressed is building for other platforms, like if you want to
One can essentially go two routes where you either have a network where you block certain subnets to prevent LAN or local access while still allowing WAN access (the runners might need to fetch stuff but we don't want them to fetch internal stuff). One can essentially go two routes where you either have a network where you block certain subnets to prevent LAN or local access while still allowing WAN access (the runners might need to fetch stuff but we don't want them to fetch internal stuff).
[This comment](https://gitea.efforting.tech/mikael-lovqvist/claude-docker/issues/2#issuecomment-36) is also relevant here. A custom egress on the VPS might make this easy to reuse across services. [This comment](https://gitea.efforting.tech/mikael-lovqvist/claude-docker/issues/2#issuecomment-36) is also relevant here. A custom egress on the VPS might make this easy to reuse across services.
## Simple deployment
For simple deployments (or as part of more complex deployments) the following pattern can be used
```bash
sudo -u nginx-user GIT_INDEX_FILE=/tmp/to-name-better git --git-dir=/gitea-data/git/repositories/mikael-lovqvist/websperiments.git --work-tree=websperiments checkout --force
```
`nginx-user` must be able to read the bare repository at `--git-dir`. The `/tmp/to-name-better` base filename should be randomized and properly cleaned up (this is a base name and has stuff tacked on, such as `index.lock` or perhaps only `.lock` - will have to investigate further).