admin/honey-be
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

gitea fixes
All checks were successful
Debug job network / debug (push) Successful in 2s
Details
Deploy to VPS / deploy (push) Successful in 53s
Details

Browse Source
This commit is contained in:
Mykhailo Svishchov
2026-03-07 20:38:06 +02:00
parent 8ce0f47258
commit 01dd290b2e
2 changed files with 14 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/GITEA_VPS_DEPLOY.md
View File

@@ -135,6 +135,7 @@ Optional secrets (workflow has defaults):
|------|--------|-------------|
| `DEPLOY_VPS_HOST` | `188.116.23.7` | Only if your Staged VPS has a different IP. |
| `DEPLOY_VPS_USER` | `root` | Only if the deploy user is not `root`. |
| `GITEA_HOST_IP` | e.g. `172.20.0.1` | If checkout fails with "Could not resolve host: server", set this to the **default gateway** seen from the job container. Run a debug job that runs `ip route show default \| awk '{print $3}'` and use that value. The workflow defaults to `172.20.0.1` if unset. |
---
@@ -292,6 +293,9 @@ git push origin main
## Troubleshooting
- **Could not resolve host: server** (during checkout)
The deploy workflow uses a manual clone via the runner host IP. Set repository secret `GITEA_HOST_IP` to the default gateway as seen from the job container (e.g. run a debug job with `ip route show default | awk '{print $3}'` and use that value, often `172.20.0.1` or `172.17.0.1`). The workflow defaults to `172.20.0.1` if the secret is not set.
- **Permission denied (publickey)**
Check: public key in `authorized_keys` on VPS, private key in `DEPLOY_SSH_PRIVATE_KEY`, no extra spaces/newlines when pasting.