ryper

Floppy is a fork of Yamtrack that seems to have only recently gotten its own name. From the notes on that release (emphasis mine):

I’m still not a professional developer; I’m an enthusiastic maintainer using AI coding tools to build the media tracker I want to use. Floppy is now a standalone project based on the incredible work of FuzzyGrim/Yamtrack, independently maintained and supported by @dannyvfilms. Yamtrack import and documented compatibility paths remain supported, but users install Floppy directly rather than treating an upstream container replacement as a migration plan.

If Pike’s fate were truly sealed his future self wouldn’t have needed to come back and tell him changing it was going to go badly for the Federation.

I don’t think there was anything that showed they couldn’t change the past; Pike just made the right choice to avoid changing it. If they tried to shoot down the missile and something went wrong, that I would maybe take as a sign the past is fixed.

I can’t help you with automation. I update my containers manually, whenever I think to do it. Nothing is accessible outside my network so I’m not worried about staying on top of security updates.

You could just build it yourself, there’s not much to it.

Dockerfile:

ARG VERSION=2

FROM caddy:${VERSION}-builder AS builder

RUN xcaddy build \
    --with github.com/caddy-dns/cloudflare

FROM caddy:${VERSION}

COPY --from=builder /usr/bin/caddy /usr/bin/caddy

My Dockerfile is under dockerfile-dns and then in docker-compose.yaml instead of pointing to an image I have:

services:
  caddy:
    build: ./dockerfile-dns

I’m not 100% sure of the right way to update it, but I think I usually use something like docker compose build --pull --no-cache.

When was the last time you checked? A client was added to the WebOS store maybe 2 or 3 years ago for recent models, and support for older models (like my C9) came months later.