Using kamal-proxy for accessories

[tommica]

Is it possible to do some kind of a reverse proxy configuration to accessories? I'd like to have multiple applications on one server, and for each of them to have their own mailpit instance, accessed by it's own sub-domain - so something like this:

APP1: foo.bar.baz.test
MAIL: mail.foo.bar.baz.test (80 -> 8025)

APP2: john.bar.baz.test
MAIL: mail.john.bar.baz.test (80 -> 8025)

[luizkowalski]

#981

[igor-alexandrov]

@djmb this issue can be closed, since #981 has been merged.

[shiny]

@djmb this issue can be closed, since #981 has been merged.

Some services require authentication or may return non-200 HTTP status codes. The proxy health check setting should accept a non-200 status codes, or offer more authentication settings.

[igor-alexandrov]

@shiny can you provide an example of such containers? My implementation of proxy for accessories has been based on PgHero service, which exposes a health check route without an authentication.

[shiny]

@shiny can you provide an example of such containers? My implementation of proxy for accessories has been based on PgHero service, which exposes a health check route without an authentication.

I am using the Docker image appwrite/resque-web, here is my deploy file

  resque-web:
    image: appwrite/resque-web:1.1.0
    proxy:
      ssl: true
      host: <host>
      app_port: 5678
      healthcheck:
        path: /
    env:
      clear:
        RESQUE_WEB_HOST: <redis-host>
        RESQUE_WEB_PORT: 6379
        RESQUE_WEB_HTTP_BASIC_AUTH_USER: admin
        RESQUE_WEB_HTTP_BASIC_AUTH_PASSWORD: <password>

Related Repo

• https://github.com/resque/resque-web
• https://github.com/appwrite/docker-resque-ui

PS
This feature has been a great help to me, thank you so much!

[igor-alexandrov]

This makes sense... As a workaround you can fork appwrite/resque-web and create a small Rack app in config.ru that won't be password protected to serve a health check route.

@djmb what do you think about the ability of adding --health-check-username and --health-check-password flags to the kamal-proxy deploy command?

[shiny]

Another situation, I'm struggling with containers that have two ports, as they are difficult to proxy.
My case is minio/minio

This is because it uses both port 9000 and 9001 — 9000 for the API and 9001 for the console.
I'm aimming to bind s3.example.com to port 9000 and console.s3.example.com to 9001. However, it seems that is not possible.

I have to directly publish the HTTP ports instead.
Another approach is separate the minio server and it's console, but this is a little bit tricky. MinIO has even removed the minio/console image.