Fixed Docker custom ports and updated docs

[clFaster]

Description

• You can override host-exposed Docker ports using the DOCKER_*_PORT variables used in compose files (for example DOCKER_POSTGRES_PORT).
• Can be set as environment var in .env file or passed with --env-file

Type of Change

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update
• Refactoring (no functional changes)
• Performance improvement

How Has This Been Tested?

Describe the tests you ran to verify your changes:

• Unit tests
• Integration tests
• E2E tests
• Manual testing

Test Configuration:

• OS: Windows 11
• Browser (if applicable): -
• Node version: v24.13.0

Checklist

• My code follows the project's style guidelines
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published
• I have signed the CLA

Additional Notes

This change makes it easier to run multiple instances on the same machine by allowing port overrides through environment variables, without editing files that are committed to Git.

[clFaster]

I noticed the docs almost exclusivly describe the profile-based workflow, but the repo still includes multiple Compose files.
Are those extra Compose files still supported for dev/prod, or are they legacy?

[therealbrad]

Both profiles and those compose files are supported. docker-compose.yml is the all-in-one file for quick setup (dev/prod profiles). The standalone docker-compose.dev.yml and docker-compose.prod.yml are used for deployments where you need finer control over which infrastructure services run in Docker vs. externally.

I found myself setting up a single PostgreSQL DB and MinIO instance for all my local deployments while developing, but wanting to run the other services inside their own docker container to keep the data separate so I thought both ways were useful.

[therealbrad]

I think it would help others to add the custom port options as comments in the .env.example file. Not completely necessary, though.

[clFaster]

I found myself setting up a single PostgreSQL DB and MinIO instance for all my local deployments while developing, but wanting to run the other services inside their own docker container to keep the data separate so I thought both ways were useful.

I see, thanks!

I think it would help others to add the custom port options as comments in the .env.example file. Not completely necessary, though.

I've added it there, with explaination how to use. Wasn't sure if it isn't confusing that they are not applied with

env_file:
  - .env.development # Load development environment variables

[therealbrad]

🎉 This PR is included in version 0.18.9 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀