also update upload script
beautifully small Python library (<200 lines) speaking the ACME protocol.
That's the protocol developed by Let's Encrypt to communicate with an automated
CA. I duly called my client "Let's Encrypt Tiny", and with less than 250 lines
beautifully small Python library (<200 lines) speaking the ACME protocol.
That's the protocol developed by Let's Encrypt to communicate with an automated
CA. I duly called my client "Let's Encrypt Tiny", and with less than 250 lines
-I think that name is still fair. For now,
-[Let's Encrypt Tiny](https://github.com/RalfJung/server-scripts/blob/master/letsencrypt-tiny)
-resides in my [server-scripts](https://github.com/RalfJung/server-scripts)
-repository, and it will stay there until anyone else has an interesting in using
-it. ;)
+I think that name is still fair. For now, Let's Encrypt Tiny resides in my
+[server-scripts](https://github.com/RalfJung/server-scripts) repository, and it
+will stay there until anyone else has an interesting in using it. ;)
+
+**Update:** Let's Encrypt Tiny now has its
+[own repository](https://github.com/RalfJung/lets-encrypt-tiny). **/Update**
The central concept of Let's Encrypt Tiny is a "certificate line" -- a sequence
of certificates, possibly for different private keys, that "belong together" in
The central concept of Let's Encrypt Tiny is a "certificate line" -- a sequence
of certificates, possibly for different private keys, that "belong together" in
unstaged, and the old TLSA record is removed from the zone.
That's it! If you have any questions, feel free to report
unstaged, and the old TLSA record is removed from the zone.
That's it! If you have any questions, feel free to report
-[issues at GitHub](https://github.com/RalfJung/server-scripts/issues).
+[issues at GitHub](https://github.com/RalfJung/lets-encrypt-tiny/issues).
-rsync ./ ralfj.de:srv/www.ralfj.de/docroot/ -aP
+rsync ./ www.ralfj.de:/srv/www.ralfj.de/docroot/ -aP