Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request] Build WithOut Traefik #72

Open
15sharpie opened this issue Aug 20, 2023 · 2 comments
Open

[Feature Request] Build WithOut Traefik #72

15sharpie opened this issue Aug 20, 2023 · 2 comments
Labels
enhancement New feature or request
Milestone

Comments

@15sharpie
Copy link

I already use another Reverse Proxy on another box on my network. With the current config the web app is routed thought the traefik so there are no ports to forward to from my already established proxy. Any chance we could get a docker compose without the traefik?

Thanks

@ElegosAkla
Copy link

If you need help to make one you should ask on the slack channel, (https://pathfinder-eve-online.slack.com)
it's not difficult from original, I may forgot something but I think you just have to:
remove traefik container, all traefik labels, et web network.
open & route, $PATHFINDER_SOCKET_HOST port on pf-socket container.
open & route, 80 port on pf.

@TyrHeimdalEVE
Copy link

Have considered making a non-traefik docker-compose.yaml file, yeah.

But @ElegosAkla is correct, you basically strip out the section:

traefik:
image: "traefik:v2.3"
container_name: "traefik"
command:
- "--log.level=ERROR"
- "--api.insecure=true"
- "--providers.docker=true"
- "--providers.docker.exposedbydefault=false"
- "--entrypoints.web.address=:80"
- "--entrypoints.websecure.address=:443"
- "--certificatesresolvers.letsencrypt.acme.httpchallenge=true"
- "--certificatesresolvers.letsencrypt.acme.httpchallenge.entrypoint=web"
- "--certificatesresolvers.letsencrypt.acme.storage=/letsencrypt/acme.json"
# Remove below line when ready for production
- "--certificatesresolvers.letsencrypt.acme.caserver=https://acme-staging-v02.api.letsencrypt.org/directory"
- "--certificatesresolvers.letsencrypt.acme.email=${LE_EMAIL}"
ports:
- "80:80"
- "443:443"
- "8080:8080"
volumes:
- "/var/run/docker.sock:/var/run/docker.sock:ro"
- "./letsencrypt:/letsencrypt"
networks:
- web
restart: always

And these:

labels:
- "traefik.enable=true"
- "traefik.docker.network=web"
- "traefik.http.services.pf.loadbalancer.server.port=80"
- "traefik.http.routers.pf.rule=Host(`${DOMAIN}`)"
- "traefik.http.routers.pf.entrypoints=web"
- "traefik.http.routers.pf-secure.rule=Host(`${DOMAIN}`)"
- "traefik.http.routers.pf-secure.entrypoints=websecure"
- "traefik.http.routers.pf-secure.tls=true"
- "traefik.http.routers.pf-secure.tls.certresolver=letsencrypt"
- "traefik.http.middlewares.redirecthttps.redirectscheme.scheme=https"
- "traefik.http.routers.pf.middlewares=redirecthttps"

Then add a ports entry like:

    ports:
      - "80:80"
      - "443:443"
      - "8080:8080"

where the above labels section was. This exposes port <OUTSIDE>:<INSIDE> and will let you point your reverse proxy to the pf container instead of traefik.

The left most part (<OUTSIDE>) can be set to other ports, if for example you already have another service listening on these ports, or use podman which as a non-privileged user that doesn't allow you to aquire these privileged ports.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants