5 ms·
Please provide Docker-less instructions. I'll happily run the TLS Proxy service on one of my servers but leave Docker out of it please.
by cutler 4y ago
Please provide Docker-less instructions. I'll happily run the TLS Proxy service on one of my servers but leave Docker out of it please.
- sfmike 4y agoOut of naive curiousity why?
- Yeahsureok 4y agoNot that person above but the install flow for docker is obnoxious on windows and mac. Having to create an account for open source software isn't reasonable, there's ways around that but not easily for most people.
- riolu 4y ago> Not that person above but the install flow for docker is obnoxious on windows and Mac. On windows it's `winget install docker`. Mac is more of the same, just drag and drop docker desktop into your Applications. You can skip the tutorials on first launch for desktop. > Having to create an account for open source software isn't reasonable, there's ways around that but not easily for most people. Creating an account is entirely optional, it doesn't even prompt you to sign in. > there's ways around that but not easily for most people. Please explain. It never requires an account at any point of the install. It never prompts for a sign in. It's entirely optional. How much easier can "not clicking the sign in button" be? You don't even need to install docker desktop, you can just use docker CLI. It doesn't even have to be docker, you can use podman. I believe OP comment is just struggling with adapting to containerized workflows. An account is not a requirement, nor is the install process difficult. If you're still wanting to do it without a container, you can just inspect the image to see what the steps are for configuring your environment yourself. It is more work to not use a container.
- Yeahsureok 4y agoFair call, I stand corrected they have changed it all again. My information is outdated but only a few years ago required you to sign up for a docker account on win and macos. Please read the SO link. I've given up on them anyway, the good faith is burnt, it's only one middle management change away from reverting to the bs of last decade. https://stackoverflow.com/questions/58133878/direct-download-of-docker-ce-installation-packages https://stackoverflow.com/questions/58133878/direct-download...
- atoav 4y agoAs someone who usually avoids docker as well: I like to know what I am running. Docker adds an extra layer of obscurity and it is typically easy to get lazy and "just run" a container. Just like you should have the habbit of checking random bash scripts you download before executing them, I think there is value in knowing the moving parts of the stuff you run.
- bartimus 4y agoSo Docker gives you Dockerfiles that show exactly what's installed. It then leverages kernel namespaces introducing that extra level of security. Or so at least that's always been how I see it.
- cutler 4y agoBecause I don't need it. I learned how to manage Linux servers in the early 2000s and that works for me. Docker on a VPS is ridiculous and wherever you find Docker you inevitably end up with Kubernetes. If I had a massive fleet of servers to manage I just might need containers but I'd probably try Chef or Puppet first. Docker is like React - designed for the needs of a global-scale internet company but now sprinkled mindlessly over sites which would be well served by a static site generator.
- neurostimulant 4y agoIt'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/Signal-TLS-Proxy/blob/main/data/nginx-relay/nginx.conf https://github.com/signalapp/Signal-TLS-Proxy/blob/main/data...
- LinuxBender 4y agoThat 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 agoDocker 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.