me/pi-ku
1
0
Fork 0
Code Issues Pull Requests Actions Projects Releases Wiki Activity

chore: remove PGDATA configuration from CI workflow
CI / Generate Certificates (pull_request) Successful in 29s
Details
CI / Frontend CI (pull_request) Successful in 1m7s
Details
CI / E2E Tests (pull_request) Successful in 6m33s
Details
ci.yml / Backend CI (pull_request) Has been cancelled
Details

Browse Source
This commit is contained in:
me
2026-05-05 18:39:17 +05:30
parent d2d8c88f69
commit 601dbd5c9b
1 changed files with 0 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.github/workflows/ci.yml
-3
View File
@@ -37,9 +37,6 @@ jobs:
POSTGRES_DB: piku_test POSTGRES_DB: piku_test
POSTGRES_USER: test POSTGRES_USER: test
POSTGRES_PASSWORD: password123 POSTGRES_PASSWORD: password123
# WHY?: gitea act runner seems to persist volumes (veryyy stubborn -_-)
# Redirecting PGDATA to /tmp ensures a fresh init every run.
PGDATA: /tmp/pgdata
ports: ports:
- 5442:5432 - 5442:5432
options: --health-cmd pg_isready --health-interval 10s --health-timeout 5s --health-retries 5 options: --health-cmd pg_isready --health-interval 10s --health-timeout 5s --health-retries 5