I am using Debian 10. It seems to me, that both journald and (r)syslogd watch for messages independently from sources such as kmesg() or syslog().
Is there any advantage to running both? Why does Debian ship with both? For comfort? I guess syslog files can be cat'd, where as journald forces you to use journalctl?
I do not want to ship my logs remotely and I have enabled journald's persistence.
I understand the initial challenge-response pattern when using Let's Encrypt, but I noticed that when testing renewals, no GET requests were hitting .well-known/acme-challenge.
Once the domain/account keys are setup, does renewal ever have to touch .well-known? Can my account/domain keys ever expire and have to be refreshed?
My app requires specific mounts to serve that directory and if possible I would like to avoid the configuration overhead if it won't ever be used anyway. I can use a slimmer setup for the initial domain verification.
I am using ufw on Alpine linux.
I have configured it in a pretty standard way:
apk add --no-cache ufw
ufw allow ssh
ufw allow http
ufw allow https
ufw limit ssh
ufw enable
rc-update add ufw default
But I am not sure if I should be setting it's runlevel to boot so I am sure it starts before any other services (ssh and docker (and therefor http/https services) are both set to start at default).
Does it matter? I don't believe alpine's RC system has a dependency setup like you might find in systemd.