systemd-resolved-docker
dnsrobocert
systemd-resolved-docker | dnsrobocert | |
---|---|---|
1 | 6 | |
16 | 547 | |
- | - | |
0.0 | 8.2 | |
about 1 year ago | 2 months ago | |
Python | Python | |
GNU General Public License v3.0 or later | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
systemd-resolved-docker
-
Lightweight DNS Server that can be run in a docker container and also allows for service discovery of other containers?
"containers auto-register themselves" that's a very broad description. systemd-resolved seems to be an option https://github.com/flaktack/systemd-resolved-docker
dnsrobocert
-
Let’s Encrypt Receives the Levchin Prize for Real-World Cryptography
If you don't feel like switching over this, I do this with dnsrobocert, with Namecheap's default DNS servers: https://github.com/adferrand/dnsrobocert
-
Trying to self host and COX is the ISP so have issues with SSL since port 80 is blocked.
I use this docker image to automate generation and updates of ssl certs: https://github.com/adferrand/dnsrobocert which I then distribute out to my other servers via nightly cron. worked reliably for years - requires you use compatible DNS provider though.
- which file server that is secure, easy, fast, stable, reliable, accessible from every devices? (no seafile, no nextcloud)
-
What is the minimum security I need for local-only services, given how hard it is becoming to avoid HTTPS.
Install this docker container: https://github.com/adferrand/dnsrobocert.
-
Bitwarden_rs + proxmox
Use: https://github.com/adferrand/dnsrobocert to setup SSL auth via a supported DNS provider.
-
How to handle SSL certificate installation (for HTTPS) when using Docker?
I use https://github.com/adferrand/dnsrobocert and then use --volumes-from to make the certs available in the other container. IIRC you can also expose the Docker socket to it and it will restart dependent containers after a certificate renewal.
What are some alternatives?
docker-pihole-dns-shim - Synchronise records founds through docker labels with pihole's custom dns and cname records.
docker-letsencrypt-nginx-proxy-companion - Automated ACME SSL certificate generation for nginx-proxy [Moved to: https://github.com/nginx-proxy/acme-companion]
SFTPGo - Full-featured and highly configurable SFTP, HTTP/S, FTP/S and WebDAV server - S3, Google Cloud Storage, Azure Blob
lua-resty-auto-ssl - On the fly (and free) SSL registration and renewal inside OpenResty/nginx with Let's Encrypt.
OpenMediaVault - openmediavault is the next generation network attached storage (NAS) solution based on Debian Linux. Thanks to the modular design of the framework it can be enhanced via plugins. openmediavault is primarily designed to be used in home environments or small home offices.
certbot-dns-cloudflare-cname - Cloudflare DNS Authenticator plugin for Certbot with support for CNAME aliasing.
FullWebsiteDemo - A complete demo on how to build, publish and host a single page application along with a backend API on your own server.
extdns - External DNS for docker-compose
letsencrypt - Certbot is EFF's tool to obtain certs from Let's Encrypt and (optionally) auto-enable HTTPS on your server. It can also act as a client for any other CA that uses the ACME protocol.
dupi-lambda - DUPI Streaming AWS Flow Log Monitor
bitwarden_rs - Unofficial Bitwarden compatible server written in Rust, formerly known as bitwarden_rs [Moved to: https://github.com/dani-garcia/vaultwarden]
lexrpc - Python implementation of XRPC + Lexicon from AT Protocol/Bluesky