updated docu

This commit is contained in:
dong.nguyen committed 2026-10-10 14:14:05 +07:00
1 parent ef3977f4be
commit 459781d251
2 files changed
+17 -1

No files matched your search

+6
View File
@@ -84,6 +84,12 @@ src/
- Deployment is triggered automatically by gitea workflow `.gitea/workflows/deploy.yml`setup in the repository. - Deployment is triggered automatically by gitea workflow `.gitea/workflows/deploy.yml`setup in the repository.
```
.gitea/
└── workflows/
└── deploy.yml
```
## Known Issues & Gotchas ## Known Issues & Gotchas
1. **React Router v8 routing:** Use `<Layout><Routes>...</Routes></Layout>`, NOT `<Route element={<Layout />}>` with nested routes — the latter doesn't pass `children` correctly 1. **React Router v8 routing:** Use `<Layout><Routes>...</Routes></Layout>`, NOT `<Route element={<Layout />}>` with nested routes — the latter doesn't pass `children` correctly
+11 -1
View File
@@ -44,7 +44,10 @@ In a VPS server, create the deployment user
```bash ```bash
sudo adduser gitea-deployer sudo adduser gitea-deployer
sudo install -d -m 700 -o deploy -g deploy /home/gitea-deployer/.ssh sudo usermod -aG docker gitea-deployer
# test user can run docker
sudo -u gitea-deployer docker ps
sudo install -d -m 700 -o gitea-deployer -g gitea-deployer /home/gitea-deployer/.ssh
``` ```
Because no ssh-copy-id is available on Windows, you need to copy the public key to the server manually. Because no ssh-copy-id is available on Windows, you need to copy the public key to the server manually.
@@ -59,4 +62,11 @@ Test ssh connected with a private key
ssh gitea-deployer@112.213.91.239 -p 2212 -i "$HOME\.ssh\gitea_deploy_key" -o IdentitiesOnly=yes ssh gitea-deployer@112.213.91.239 -p 2212 -i "$HOME\.ssh\gitea_deploy_key" -o IdentitiesOnly=yes
``` ```
Get content of private key
```powershell
Get-Content -Raw "$HOME\.ssh\gitea_deploy_key"
```
In Gitea, create action secrets `DEPLOY_HOST`, `DEPLOY_SSH_PORT`, `DEPLOY_USER`, `DEPLOY_SSH_PRIVATE_KEY` for deployment.