4 ms·

It's basically just spin up nginx acting as a relay to proxy requests to Signal's server. Here is the nginx config for the relay: https://github.com/signalapp/

• LinuxBender 4y ago
  That is very straight forward and simple. Is there really nothing else to this? Is the reason for docker so that they can update the nginx mapping and people's containers will automatically update? I might port this config over to HAProxy personal preference reasons
  • neurostimulant 4y ago
    Docker compose doesn't work like that. People that uses it must pull the new dockerfile/config first, stop the container, rebuild it again using `docker-compose build` and start the container again. Nothing automatic about it. I suspect the mapping is pretty much set in stone because many people won't go out of their way to update their instance. IMO it would be better if they release a pre-built image in docker hub so people has easier time hosting it on other container platforms instead of just docker compose.