Streamlined and added CI steps for docker compose

[tobiasmcnulty]

This PR makes several improvements to streamline the local Docker setup process:

1. Moves the Trac schema/table creation script out of the entry point and into a one-time initialization script, to avoid Postgres errors when it's inadvertently re-run when the web container is restarted.
2. Moves the management commands that create data out of the Docker entrypoint and into their own reset-local-db Makefile target.
3. Updates the Docker instructions with the applicable *.djangoproject.localhost:8000 links and ties back to the non-Docker setup.
4. Runs tests via Docker, to avoid reoccurrences of Docker only install instructions run into database connection error trac does not exist #2193 (or similar)

[Copilot]

Pull Request Overview

This PR streamlines the Docker development setup by improving the initialization process and adding comprehensive test execution via Docker. The changes simplify the dev entrypoint script, reorganize database initialization, and provide clearer documentation for Docker-based development workflows.

• Moved database initialization logic from the dev entrypoint to dedicated initialization scripts
• Added a new Makefile target for resetting local development data
• Enhanced GitHub Actions workflow to run tests via Docker Compose

Reviewed Changes

Copilot reviewed 7 out of 8 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
docker-entrypoint.dev.sh	Simplified by removing database initialization commands that are now handled elsewhere
docker-entrypoint-initdb.d/02_trac_schema.sh	New script to handle Trac database schema initialization during container startup
docker-compose.yml	Updated volume mounts to use the new initialization directory structure
README.rst	Enhanced Docker documentation with clearer step-by-step instructions and additional usage examples
Makefile	Added reset-local-db target to consolidate database reset commands
.github/workflows/docker-test-build.yml	Added Docker Compose setup and test execution for the tests.txt matrix
.dockerignore	New file to exclude unnecessary directories from Docker build context

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[tobiasmcnulty]

Hi, @easherma! Thanks again for your helping improving the Docker setup at the sprints. Would you be up for giving this a review when you have a moment? No rush.

[ulgens]

I added a small comment about the migrate command call, but other than it looks nice 🌻

[SaptakS]

@tobiasmcnulty makes sense to me. I think you need to rebase and resolve conflicts though. Once that is done, I think should be ready for approval.

[CuriousLearner]

For production, we just build the image, and then nothing else? 🤔

[CuriousLearner]

I think just building the image will be a weak test (and burn CI minutes). Since we are building the image, we might also want to check the startup, something like:

- if: matrix.req_file == 'prod.txt'
  name: Test production image starts successfully
  run: |
    docker compose up -d
    sleep 5
    docker compose ps
    docker compose logs
    # Maybe curl a health endpoint

[tobiasmcnulty]

@CuriousLearner Thanks for the feedback. Having some tests for the production image sounds like a positive change to me. I think it could be its own PR as its not really related to the local docker compose setup.