Replies: 1 comment
-
This sounds like a docker compose networking question. https://docs.docker.com/compose/networking/ is a useful first source of info, but it seems to me that the URL will simply be For the exposed service, you should be able to reach it outside of docker-compose with There may be a problem with the host being set as discussed in simple-repository/simple-repository-server#5. It will be fixed when the line at https://github.com/simple-repository/simple-repository-server/blob/be716cb814d2d828ed16f671cd795c88fdfa70dc/simple_repository_server/__main__.py#L36 is in a release. Overall, your setup looks to be in fairly good shape 👍 |
Beta Was this translation helpful? Give feedback.
-
Motivation
So the above picture describes the setup I would like to realise and currently exploring if I can do that.
For now I try to get the server and the web service running. For test purposes I do that in a Docker compose setup.
Docker Setup
Compose file:
services: frontend: container_name: web-service build: dockerfile: Dockerfile-frontend context: ./dockerfiles ports: - '8081:8081' backend: container_name: server build: context: ./dockerfiles dockerfile: Dockerfile-backend ports: - 5432:5432
Dockerfile web service:
Dockerfile backend:
(I use bookworm only for testing, as I am more familiar in a debian based system, final deployment would most likely be alpine linux based)
Current Status
So in the first iteration I only want to test this with a public gitlab endpoint, but actually have a two simple questions:
Beta Was this translation helpful? Give feedback.
All reactions