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.

I have a docker forgejo runner for CI with Codeberg. Where did you get stuck?

On second read, maybe you already knew that.

A virtual environment is just a copy of the python and pip binaries. When you activate the venv, the venv dirs temporarily get added to your path, so your regular python alias points to the binary in the venv (run which python with venv active to verify). Pip will install modules to a subdir of your venv. It basically works like npm and the node_modules dir.

Thanks. Do you host five filters? Do you pay for it?

Would you mind elaborating a bit? I’ve been looking into good rss solutions lately and blogs without a feed were where I got stuck. How do you use five filters? How do the two components work together?

Edit: Also, some sites WITH a feed like Pitchfork are next to useless when all you get is the headline.

There’s an ongoing feature request about recurrence on the Nextcloud github. There was mention that using a client that supports it is no problem, but to be careful not to mark a task as complete on the web UI, as that would remove the entire task instead of marking one repetition as complete.

Is there a specific reason you’re taking the services down before bringing them back up? Just docker compose pull && docker compose up -d recreates all services that had a new image pulled, but leaves the others running.

That’s painful to look at. You can do markdown code blocks with triple-backticks `

The star, of course, being the almost universally accepted sign for “entrance” in braille++. Or “exit” in certain dialects, conveniently.

… and enhanced by a sentence or two why it is worthwhile. Getting really tired of the no-effort link drops around here. Better yet, the same no-effort link drop to multiple similar communities on various instances.

Is there a block function for link-only posts?

Are there filters to prevent seeing duplicate content?

I have done a similar thing in the past, but to flash firmware onto any device with a certain USB descriptor that gets plugged in. It was a mess of USB hubs and cables, but it worked.

What I did was write a udev rule that checks for the vendor and product id of a newly plugged in device and calls a script when there’s a match. The script then performs the flashing and logs the output.

In your case:

1. dd the source USB to a file (make sure the partition you’re dding is smalled than any target drive
2. Udev rule according to your needs (all the same product or different drives?)
3. Script that dds the file you created earlier back to the newly plugged in drive.

Edit. Did this on a rpi3