docker-nginx VS berty

Add a brief sleep to the Nginx container's CMD. The default is CMD ["nginx", "-g", "daemon off;"], so something like command: ["sleep", "4", "&&", "nginx", "-g", "daemon off;"]. Didn't try this so not sure whether it'll work or not. Glancing at their docker-entrypoint.sh this will disable autoconfiguration from /docker-entrypoint.d/ (sigh).

A few time ago, I created the this post about nginx official image ENTRYPOINT "issue": https://github.com/nginxinc/docker-nginx/pull/752 .

An alternative to this approach, you could also write a template Dockerfile and then write some shell script that you would run locally to take that template and then write/generate Dockerfiles for each. Many of the official Docker images are setup and built this way. Here is an easy example of the nginx Docker image repository. https://github.com/nginxinc/docker-nginx It has three different templates in the root of the repository and has the update.sh script that is run to take those and write them out to a directory and essentially do a find and replace on the templates in the template. Those generated directories are then committed to the repository and pushed up to be built and published as Docker images.

It's a bit odd to use a custom docker image, rather than the one maintained by nginx Inc though:

https://github.com/signalapp/Signal-TLS-Proxy/blob/main/ngin...

Vs

https://github.com/nginxinc/docker-nginx

For one, this is 5 versions behind (1.18 vs 1.23).

In general seems caddy or haproxy might be a better fit - but nginx is a perfectly fine choice I suppose.

The container image docker.io/library/nginx will hopefully soon have support for socket activation. My PR got merged 9 days ago but the current image does not yet have the funcationality.

} ``` I have fixed the templates at https://github.com/nginxinc/docker-nginx/pull/533

Not written in Rust, but may be Berty can give you some ideas?

Berty is an open source, secure, private, censorship resilient messaging protocol. Berty is designed to work with NO internet connection. Thanks to Bluetooth LE and mDNS, messages can be securely and privately relayed, peer to peer to create an adhoc network. Of course old fashioned networks still work, and if you’re connected to a “hostile” network that’s being surveilled, the Berty protocol can still operate safely and securely thanks to e2e encryption. Super nice!

Berty: Privacy-first messaging app\ (34 comments)

Well, in fact they have a CLI client ( that I haven't tested ) [1] and their site says they're going to be available also for Mac, Windows and Linux.

https://github.com/berty/berty