Your favorite lesser known docker container?

Have you tried beaver docking? I really like it. I just learned of it recently and do it everyday. Better than a lot of other docking.

Yeah, it's not perfect, but it works well enough to get what I wanted: see unexpected expenses from my vast array of credit cards. I've caught fraudulent transactions my bank didn't, so that's nice.

I don't actually do strict budgeting with it, I mostly just want to see generally where our money is being spent, and I prefer to keep those transactions as private as possible (well, outside of my banks selling my transaction data to data brokers, that is...).

Firefly

Nope. I found AB and saw that they had experimental support for SimpleFIN, which supports financial institutions in my country (USA), and it was cheaper than my old, non-selfhosted solution (Tiller). SimpleFIN provides a pretty simple API, so there's no reason Firefly couldn't support it as well (and there's an issue for it).

I also really hate PHP, so the fact that Actual Budget is written in node.js is a plus.

I thought I replied to this earlier, but it seems like it didn't take.

Pushover seems nice, but doesn't seem to be self-hostable. It looks like there is a replacement service in the works called Overpush.

All I can say is that I don't own any Apple products and never even looked at that section of their documentation. The Android and web clients work flawlessly, except that the Android client doesn't support markdown.

Right. When a request comes in, Traefik, for one, will hold the connection until the service is back up then forward the request as usual. This works for UIs as well. You'll get a temporary loading page then redirected to the requested UI when the service is up.

How would the timed tasks be handled if they're offline

It probably would work well with those as long as the startup time was quick (my containers come up almost instantly) and the initiating clients can handle a bit of latency. I didn't notice any hiccups in my use at all.

Node-RED requires enough technical knowledge that it becomes not easier, but harder than writing JS code when things go medium size. N8N is superior in UX.

Also although I greatly appreciate everyone’s efforts, I don’t want to rely on community plugins that require maintenance and may or may not abandoned after it’s developer loses interest/move on with their life. TBH NPM is brimming with those.

Haven't tried node, so I'm interested to hear as well, but n8n is super easy to set up, and I like the interface.
I've looked at node multiple times in the past, and I remember finding no reason to switch.

Yeah, businesses went big in N8N but home users are somehow unaware of it. It even has Home Assistant integration.

You need to install the client from F-Droid and it periodically polls your device for its location.

I used Traccar before switching to FMD. It used a lot of battery for somewhat inaccurate results in my case (might be phone related).

the only change I had to make was to add the config file to the volumes list:

services:
  fmd-server:
    image: registry.gitlab.com/nulide/findmydeviceserver:v0.7.0
    container_name: fmd-server
    volumes:
      - data:/data
      - ./fmd/data:/fmd/db/
      - ./fmd/config/config.yml:/fmd/config.yml:ro
    restart: unless-stopped
    networks:
      - fmd_server
#    ports:
#      - 8080:8080

# legacy
volumes:
  data:

networks:
  fmd_server:

No, mostly because Google Search is just terrible. The app itself is great.

At least with Searx you can search multiple private search engines (your preference) at once. You can also selfhost it.

I used it to display the Home Assistant UI on an old iPad 2 which didn't support the app or even the Web UI through Safari.

Bypassing work sandboxing

Firewall bypass _°!°

Been working untouched for a long time but might be time to update. To that maintained one, thanks!

My point is you can make Dockerfiles do a lot of things