ello learns

nginx

I use fail2ban as my server watchdog. Among the sensible defaults it hands me is a file path pattern that uses a wildcard to hoover up my nginx access logs:

nginx_access_log = /var/log/nginx/*access.log

Super convenient, except that pattern gets evaluated when fail2ban starts up, and never again. If your server starts writing more logs that match the pattern — say if you launch a new site and direct its logs to a new file — your fail2ban jails that use the nginx_access_log path variable won't see them until it restarts. And then you'll be looking at the server logs and the ban logs and testing things with fail2ban-regex and have no idea why people doing bannable things are not getting banned.

Anyway restart fail2ban sometimes. You know, just in case.

#fail2ban #nginx #sysadmin

from @ello@void.ello.tech

It's the last puzzle piece for this lil' blog o' mine: image hosting.

The hosted version of #WriteFreely, write.as, will do image hosting for you with their paid snap.as service. I'm running the open-source self-hosted version, so I'm on my own.

I wanted something lightweight and easy to maintain with roughly the user experience of #imgur:

  • No gallery nonsense, this is just for individual storage and retrieval
  • Let me paste images directly from my system clipboard, no mucking about with my local file system
  • Everything is public but read-only, so everybody can see what I upload but I'm the only one who can upload
Read more...

hello

Hello is this thing on

Hi? Hi. You're here. I'm here! I think I'm live?

Let's just get down to brass tacks. Writefreely has a setup guide, and somebody named Karl wrapped it all up into a Dockerfile. I borrowed heavily from both resources to end up here. I'm not putting my configs in a nice repository to share because they're probably terrible and should not be used by anyone, but they seem to be working so I'll talk about them.

Read more...