Use docker network instead of exposing all ports manually #1859

Closed
opened 2026-04-05 16:36:16 +02:00 by MrUnknownDE · 0 comments
Owner

Originally created by @TobiasGrether on 7/17/2023

Title of this pull request?

Use docker network instead of exposing all ports manually

Small Description?

Currently, the ports of all service components are exposed manually through the docker compose file. This is unnecessary, since only the nginx proxy and the services between each other need to communicate.

Pull Request Checklist:

  • Please make sure all jobs pass before requesting a review.
  • Put closes #XXXX in your comment to auto-close the issue that your PR fixes (if such).
  • Have you lint your code locally before submission?
  • Did you write tests where appropiate?

Screenshots (if appropriate):

*Originally created by @TobiasGrether on 7/17/2023* ### Title of this pull request? Use docker network instead of exposing all ports manually ### Small Description? Currently, the ports of all service components are exposed manually through the docker compose file. This is unnecessary, since only the nginx proxy and the services between each other need to communicate. ### Pull Request Checklist: - [ ] Please make sure all jobs pass before requesting a review. - [ ] Put `closes #XXXX` in your comment to auto-close the issue that your PR fixes (if such). - [ ] Have you lint your code locally before submission? - [ ] Did you write tests where appropiate? ### Related Issue? ### Screenshots (if appropriate):
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/oneuptime#1859