Posts / selfhosting

The Weekend Project You Open Twice a Year


There’s a thread on r/selfhosted at the moment asking people to confess to the service they spent a whole weekend setting up and now open maybe twice a year. The original poster’s answer was a pair of elaborate observability dashboards, built “for science”, checked only when something breaks. They still won’t tear them down.

I read it twice. I recognised myself both times.

The most common answer by a wide margin was paperless-ngx. It’s a document management system. You scan your paper, it reads the text, tags it and files it, and you can find anything in seconds. It’s a good piece of software. People install it with great intent and then it sits there, patiently, like a gym membership.

One person said they still intend to use it, years after installing it. Another said they only ever send documents in and rarely look at them. A third said they’d set up an email rule so receipts and bank statements flow in automatically, and that this was what finally made it stick. Someone else admitted they have it archiving their Gmail attachments, and when they need one they search Gmail and forget Paperless exists.

That last one made me laugh out loud, in the quiet way you do in a home office when your daughter is on a call next door.

The scanner is the whole story

The thread had a theme running through it that I think is the real lesson. The software was never the problem. The scanner was.

People talked about getting an Epson to drop files into a watch folder over SMB. Someone else said a Brother scanner that sends to an FTP folder was the thing that changed everything. Another said a small scanner by the front door, where you open the mail and feed it straight through, made the habit automatic. The installs that lived were the ones where a physical object removed the friction. The ones that died were the ones that needed a human to remember.

I know this one personally. I have a pile of paper on a shelf in the study. It has a tax summary in it, a warranty for a dishwasher we replaced two years ago, and something from the council I’m fairly sure matters. A perfectly good paperless system would fix this. I’d just have to start by scanning the pile, and the pile is where my enthusiasm goes to die.

It’s the opposite of a game that respects your time. Dark Souls is hard, but every hour you spend in it goes somewhere. A badly configured document pipeline is hard in the dull way, and at the end you have a folder.

Why we build them anyway

I don’t think the weekend setup is wasted. Mostly it isn’t about the service. It’s a puzzle with a clear finish line, and you get to feel competent for forty-eight hours. At work my days are tickets, pipelines and meetings about pipelines. At home I can pick something small, make it work and be done. The dashboard doesn’t have to earn its keep. The doing was the point.

There’s a cost, though, and I’d be kidding myself if I skipped it. Every one of these things is a container running on a machine that’s drawing power, needing updates, and waiting to break at 11pm on a Sunday. I spend my working life telling people that unmaintained systems are a liability. Then I go home and run seven of them. I hold both views and I haven’t found a way to make them agree.

What I’m taking from it

The useful bit of advice buried in all the confessions is simple. Before you build the thing, build the way stuff gets into the thing. If getting data in takes any thought at all, you’ll stop doing it by March.

So I’m going to buy a cheap sheet-fed scanner, put it next to the letterbox, and see what happens. If the pile on the shelf gets smaller, I’ll count it a win. If it doesn’t, I’ll have a very nice scanner and a dashboard I check twice a year.

I’m at peace with either outcome. Mostly.