absc

If you need to save state across executions, you should write a daemon instead.

I have one OpenBSD VM running on vultr with:

- Mail server (OpenSMTPD)

- IMAP (Dovecot)

- CVS server for my projects.

- httpd(8) for my website.

I still need to add rspamd for spam check. But insofar, I received just one spam E-mail.

Definitely just a routing hicup with my provider (I think). Sorry for the noise.

Just an update. I can properly resolve the DNS of tarsnap.com. It smell like a routing problem as all the connections to a aws IP simply times out.

If it's for you, it's maybe some hiccup in my zone (Italy)

Oooook, so it seems to be something here in my zone (Italy). Need to check why then. Maybe it's the DNS I'm using (quad9)

I generally agree with the article. Personally, I don't log _that_ many informations in my applications.

Normally, my users will just dump the whole log in an e-mail with a "doesn't work" message attached.

IMHO, a logging facility should grow with the project and I think the standard logging package in go is the right size.

About bubbling up the errors: absolutely! Always let the caller handle it!

Forgot the link:

https://tarsnap.com

I use tarsnap for off-site backups. It has a reasonable price, even for some GB of data

Been there. At my actual job (a small IT firm in Europe), my boss spent almost half a year searching for somebody to hire. All the times it was like "they are too old", or "don't know enough", or just for a different POV.

In the meantime, collegues are leaving the gig, making my level of stress go up.