fix: Gitea Traefik routing and connection pool optimization
Some checks failed
🚀 Build & Deploy Image / Determine Build Necessity (push) Failing after 10m14s
🚀 Build & Deploy Image / Build Runtime Base Image (push) Has been skipped
🚀 Build & Deploy Image / Build Docker Image (push) Has been skipped
🚀 Build & Deploy Image / Run Tests & Quality Checks (push) Has been skipped
🚀 Build & Deploy Image / Auto-deploy to Staging (push) Has been skipped
🚀 Build & Deploy Image / Auto-deploy to Production (push) Has been skipped
Security Vulnerability Scan / Check for Dependency Changes (push) Failing after 11m25s
Security Vulnerability Scan / Composer Security Audit (push) Has been cancelled
Some checks failed
🚀 Build & Deploy Image / Determine Build Necessity (push) Failing after 10m14s
🚀 Build & Deploy Image / Build Runtime Base Image (push) Has been skipped
🚀 Build & Deploy Image / Build Docker Image (push) Has been skipped
🚀 Build & Deploy Image / Run Tests & Quality Checks (push) Has been skipped
🚀 Build & Deploy Image / Auto-deploy to Staging (push) Has been skipped
🚀 Build & Deploy Image / Auto-deploy to Production (push) Has been skipped
Security Vulnerability Scan / Check for Dependency Changes (push) Failing after 11m25s
Security Vulnerability Scan / Composer Security Audit (push) Has been cancelled
- Remove middleware reference from Gitea Traefik labels (caused routing issues) - Optimize Gitea connection pool settings (MAX_IDLE_CONNS=30, authentication_timeout=180s) - Add explicit service reference in Traefik labels - Fix intermittent 504 timeouts by improving PostgreSQL connection handling Fixes Gitea unreachability via git.michaelschiemer.de
This commit is contained in:
26
docs/codex/guidelines.md
Normal file
26
docs/codex/guidelines.md
Normal file
@@ -0,0 +1,26 @@
|
||||
# Codex Agent Guidelines
|
||||
|
||||
This document supplements `AGENTS.md` with Codex-specific working notes. Always treat `AGENTS.md` as the source of truth and keep this file aligned with future updates.
|
||||
|
||||
## Core Expectations
|
||||
|
||||
- Obtain explicit approval from the project owner before attempting any code change or file edit.
|
||||
- Follow every checklist item in `AGENTS.md`, including framework principles, testing strategy, and tooling conventions.
|
||||
- Keep documentation edits consistent with project tone (PSR-12 code examples, ASCII character set, precise terminology).
|
||||
|
||||
## Workflow Notes
|
||||
|
||||
- Prefer small, reviewable steps and clearly report what changed, including file paths and line references.
|
||||
- When a task involves multiple steps, draft a lightweight plan unless the work is trivial.
|
||||
- Record unanswered questions or ambiguities in the final message so the owner can respond quickly.
|
||||
|
||||
## Tooling Reminders
|
||||
|
||||
- Use `bash -lc` shell invocations with explicit `workdir` as required by the Codex CLI harness.
|
||||
- Rely on `rg` for searches; fall back to alternatives only if `rg` is unavailable.
|
||||
- Do not run container or network commands without explicit permission when sandboxed.
|
||||
|
||||
## Documentation Maintenance
|
||||
|
||||
- Update this file whenever Codex-specific guidance changes so it remains synchronized with the rest of the ecosystem docs (e.g., keep parity with `docs/claude/` where it makes sense).
|
||||
- Coordinate with the project owner before introducing new sections or workflows that impact other agents.
|
||||
Reference in New Issue
Block a user