Move hardcoded E2E admin password to Gitea secret #128

New Issue

marcel · 2026-03-28T08:40:09+01:00

marcel commented

2026-03-28 08:40:09 +01:00

Priority: high

APP_ADMIN_PASSWORD=admin123 and E2E_PASSWORD=admin123 are hardcoded in plain text in .gitea/workflows/ci.yml (lines 144 and 192). This credential is now part of the repo's git history and visible to anyone with repo access.

What to do

Create a Gitea secret E2E_ADMIN_PASSWORD in the repo settings (Settings → Secrets).
Replace the hardcoded values in ci.yml:

# Start backend
--APP_ADMIN_PASSWORD=${{ secrets.E2E_ADMIN_PASSWORD }}

# Run E2E tests env block
E2E_PASSWORD: ${{ secrets.E2E_ADMIN_PASSWORD }}

Note: the credential is also in git history. If this repo is or ever will be accessible outside the local network, rotate the credential after fixing this.

**Priority: high** `APP_ADMIN_PASSWORD=admin123` and `E2E_PASSWORD=admin123` are hardcoded in plain text in `.gitea/workflows/ci.yml` (lines 144 and 192). This credential is now part of the repo's git history and visible to anyone with repo access. ## What to do 1. Create a Gitea secret `E2E_ADMIN_PASSWORD` in the repo settings (Settings → Secrets). 2. Replace the hardcoded values in `ci.yml`: ```yaml # Start backend --APP_ADMIN_PASSWORD=${{ secrets.E2E_ADMIN_PASSWORD }} # Run E2E tests env block E2E_PASSWORD: ${{ secrets.E2E_ADMIN_PASSWORD }} ``` Note: the credential is also in git history. If this repo is or ever will be accessible outside the local network, rotate the credential after fixing this.

marcel added the phase-1: security label 2026-03-28 08:51:18 +01:00

marcel referenced this issue

2026-03-28 08:53:06 +01:00

Create .env.example and DEPLOYMENT.md for production onboarding #139

marcel referenced this issue

2026-03-28 10:31:43 +01:00

Add build-and-push and deploy jobs to CI workflow #142

marcel added the devops label 2026-03-28 10:47:25 +01:00

Sign in to join this conversation.