Airtable or nocodb might be suitable for this. Or Nextcloud Forms. But hard to advise since it’s not clear if your focus is on data entry or visualization.

I’m low key on the lookout for something like this as well, to gain independence from mail providers, and I’ve had a browser tab for Mail Archiver open for a few months now but never got around to trying it out. Maybe this would solve your problem?

This looks friendly. I gave up setting up Authelia after my last attempt, but I might give it another go with this when motivation hits me. Some documentation for Traefik integration would be nice.

I wasn’t advocating to get a J4125 in 2025, I was sharing my experience with it. I can’t confirm it choking with Jellyfin.

I’m doing everything you list and quite a bit more on a QNAP with a Celeron J4125. A fraction of the cpu performance you’ll have, yet very capable of all the tasks I ask of it. 16gb of memory is a good starting point I think.

What does your build come out at?

“Just” some highly specific VM settings, in the end. I don’t know much about that, and terms like qemu don’t mean anything to me so I followed blog posts until it worked. (This one and maybe this one, I think.) It’s possible that it is actually trivial.

It’s been a while, but I can look up what I have when you need it. Feel free to ping me!

Yes, it was exactly that: Once I got the NICs set up the way I wanted them it was a breeze and everything just works. And I really like that I made every part work myself, no magic. I learned a lot, and wouldn’t have had I relied on Proxmox fiddling with the right parts for me.

I was in a similar spot not too long ago, setting up a firewall and general network box. I was going to go with Proxmox but a fellow Lemmy guy strongly advocated for Incus on top of vanilla Debian. I was intrigued and ended up going for it. Learned a lot about networking with systemd (bridging, IP assignment and so on) for things I could have gotten for free in Proxmox (literally a few clicks), and had to fight Incus to work with a FreeBSD VM for Opnsense, but I love the setup now. Pure debian with a few Incus VMs and Docker inside of those as needed. So clean!

How about Donetick?

As a first step, why don’t you try to trigger a rescan sudo -u www-data php occ files:scan --all

If that doesn’t improve things, try to find and delete the image file the log complains about misc/m-t0627-01511-00434 (2).jpg.

Still nothing after that, I’d try to hunt down individual contacts in the DB.

What happens if you delete this contact from the web UI?

Edit: Unclear whether the web UI is functional. If it isn’t, try deleting it from the database directly.

Using it to backup from a QNAP. Works very well and hassle-free. I’m using the QNAP backup app, but would be just as easy with any other tool. Just make sure to encrypt the backups.

Does this do/can it be used for keeping track of bicycle maintenance? Mostly which components are used (tires, brake pads,…) and when maintenance was done and so on?

I think OSMC does this.

You can set up your project in a private repo and in your deploy action push it to the main branch of your public Pages repo. I agree it’s not a huge deal to show the source, but I prefer it like that.

name: Deploy Hugo site to Github Pages

on:
  push:
    branches:
      - main
    workflow_dispatch:

jobs:
  build:
    runs-on: ubuntu-latest

    steps:
      - name: Checkout repository
        uses: actions/checkout@v4

      - name: Set up Hugo
        uses: peaceiris/actions-hugo@v3
        with:
          hugo-version: "0.119.0"
          extended: true

      - name: Build
        run: hugo --minify

      - name: Configure Git
        run: |
          git config --global user.email "you@example.com"
          git config --global user.name "Your Name"
      - name: Deploy to GitHub Pages
        env:
          GITHUB_TOKEN: ${{ secrets.DEPLOY_TOKEN }}
        run: |
          cd public
          git init
          git remote add origin https://user/:${{ secrets.DEPLOY_TOKEN }}@github.com/USER/USER.github.io.git
          git checkout -b main
          git add .
          git commit -m "Deploy site"
          git push -f origin main

edit: Markdown is adding a / after “user” in above git remote command. Don’t know how to get rid of it.

My Nextcloud journey went from a Raspberry Pi 2B with a single USB HDD over a Pi 3B to a QNAP 2bay NAS on RAID 1 with a proper backup strategy including daily encrypted cloud backup. Having come to rely on the setup much more than when I was starting out playing with it years ago, I sleep much easier now. That said, I never lost any data, even on very questionable hardware without any redundancy whatsoever.

If you’re not very set on hosting at home, hosting a static Hugo page directly on Github Pages is incredibly convenient and easy (and free.) With the right Github Action, updating the site is as simple as pushing content to the main branch and it automatically deploys. And should Github ever give you a reason to do so, moving away is as simple as copying your static files to any other webhost and pointing your domain there instead.

Edit: It’s of course equally easy to deploy on your NAS - just a basic nginx serving the directory with your static site that Hugo generated.

Are you looking for advice regarding administration or the platform?

I say for a simple blog it’s hard to beat Hugo. There are plenty of nice themes and easily adjustable, too with a bit of html/css.

I need to use the IP for specific reasons concerning my setup; and I don’t want the two containers to share a Docker network.

This used to work exactly as is when I set it up, but doesn’t anymore.

I tinkered with it some more now and I found that while I can ping the docker host, I can’t actually wget anything from any docker services from within the Homepage container. Currently at a loss why that might be.

Would love to see it.

Here’s mine from the Paperless compose.yml (non functional):

  webserver:
    image: ghcr.io/paperless-ngx/paperless-ngx
    [...]
    labels:
      - homepage.group=Productivity
      - homepage.name=Paperless
      - homepage.icon=paperless.png
      - homepage.href=https://[LOCAL URL]
      - homepage.description=Document Management
      - homepage.widget.type=paperlessngx
      - homepage.widget.url=http://[PAPERLESS IP:PORT]
      - homepage.widget.key=[PAPERLESS API TOKEN]

And here’s the error from Homepage frontend:

    API Error: Unknown error
    URL: http://[PAPERLESS IP:PORT]/api/statistics/?format=json
    Raw Error:
    {
        "errno": -110,
        "code": "ETIMEDOUT",
        "syscall": "connect",
        "address": "[PAPERLESS IP]",
        "port": [PAPERLESS PORT]
    }

I don’t think it’s you. The paperless widget stopped working for me recently after it had been fine before. Similar setup to yours.

It bothered me a little but since the widget isn’t actually very useful to me I didn’t care to invest more time to get to the bottom of it.