There were old wrappers that emulated sendmail but reformatted the message for use with gotify and such

Well, I wouldn’t go that far. Let’s not forget Nextcloud started as a fork for the same reason. The permissive license doesn’t stop us from keeping it alive, but it is something to be cautious of.

I’m curious about opencloud. It’s flashy, uses go, and has everything that I’m actively using in Nextcloud. The license does make me a little cautious about it though. Apache v2 on the server side is unusually permissive. AGPLv3 on the web ui is cool, but it’s also not really helpful if you’re not required to publish server changes.

https://wiki.archlinux.org/title/Podman#Quadlet

It does, but it’s disabled by default. It’s explicitly for docker compatibility though, not a core part of the application.

You shouldn’t need to use the aur unless cachy is restricting your repo access. It’s all in arch extras.

You have the potential to run into issues if the device is externally managed. At&t likes to push firmware updates at early hours. Cutting power during one of those would be problematic.

Don’t forget about linkwarden

I use the linuxserver images for Nextcloud. Have worked pretty well for me over the past few years.

https://hub.docker.com/r/linuxserver/nextcloud

Yeah, that thing is honestly impressive. If I didn’t already have a full network manager wg setup I’d just use that.

Reformatting that compose for people:

version: "2.1"                                                services:
  wireguard:
    image: linuxserver/wireguard
    container_name: wireguard
    cap_add:
      - NET_ADMIN
      - SYS_MODULE
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Asia/Singapore
      - SERVERURL=auto #optional
      - SERVERPORT=51820 #optional
      - PEERS=1 #optional
      - PEERDNS=auto #optional
      - INTERNAL_SUBNET=10.13.13.0 #optional
    volumes:
      - ./config:/config
      - /lib/modules:/lib/modules
    ports:
      - 51820:51820/udp
    sysctls:
      - net.ipv4.ip_forward=1
      - net.ipv4.conf.all.src_valid_mark=1
    restart: unless-stopped

Sounds like you didn’t read the extended manual: https://github.com/linuxserver/docker-wireguard

There are a lot of other configs for that container that must be provided before startup. It’s just a generic runner. If you want it to run as a server you need to follow this section: https://github.com/linuxserver/docker-wireguard?tab=readme-ov-file#server-mode

Are you at getting the handshake in the app? If so, you’re probably just missing the dispatch commands for traffic masquerading.

Eaton is your best bet for compatibility in the consumer market.

https://networkupstools.org/stable-hcl.html

Yo, they added full page copies now? Gotta give it a spin again

To me on the security side of things caddy has a feature I have yet to see anywhere else: default reverse proxy headers.

Got something you want to lock down remote js loading on unless it explicitly requests an override? Default the variable to a locked value. The application can override it with it’s own header as necessary.

https://caddyserver.com/docs/caddyfile/directives/header

deleted by creator

I wish nginx had the concept of default header values for reverse proxies…

I mean, you can kind of do it with macros but man…

If you’re just looking for RSS -> Push take a look at feedpushr

I use it with gotify without too many issues.

You say that like there a large overhead to containers…

Even in this case that overhead is negligible. Container configs and artifacts are also more portable and easier to backup.

It was dead however long ago when I submitted a PR. Still unmerged with no activity on the request so I just never went back to check.

It’s good to hear that they are working on it again though, if that is the case.

It depends on what you want. Do you want containers that don’t blow away your firewall? Podman is nice, but docker can be configured a little to avoid this. Want things that autostart and don’t have issues with entry points that attempt to play with permissions/users? Docker or podman as root is necessary. Want reasonable compose support? Podman now needs a daemon/socket. Want to make build containers and not deal with permission/user remapping at all? Podman is really nice.

Do not attempt to use podman-compose. That app is dead.

Unfortunately if you want to make tools that will be used by other people then you must add docker support. It just owns too much of the market.