• 1 Post
  • 10 Comments
Joined 1Y ago
cake
Cake day: Jun 23, 2023

help-circle
rss

Maybe give cloudflared a try. Works for me even with nextcloud’s ssl (don’t think there’s a way to start NC without the self-signed cert). Couldn’t get it to work with NPM (I admittedly don’t know much about nginx) so I brought in the big gun(s).


Backblaze b2, borgbase.com. There are also programs like dejadup that will let you backup to popular cloud drives. The alternatives are limitless.


I’ve hosted invidious relatively easy for a while now. Simple UI and just works. If anyone needs my compose and config setup, reply and I’ll post it.


They provide the best balance for efficiency. Not too powerful enough to be a workhorse and not to weak to run multiple simple applications/services. NUCs are great in that they come with hardware video acceleration tech that’s highly optimized for media transcoding.


For accessing your VPN network outside of your LAN, there’s the shadowsocks option in the gluetun wiki.


Jellyfin, AdGuard Home, Nextcloud, Syncthing, Invidious, SearxNG


No worries. I ended up writing a systemd service that restarts the npm container a minute after the watchtower runs. I don’t know why I didn’t think of that earlier but I guess it’s a much simpler solution than using depends_on with npm which hosts a lot of my other services.


I want to restart the NPM container (when the searxng service goes down) instead of searxng.




How to trigger a container restart based on successful update/image change of another container?
Basically have watchtower monitor and update containers whenever new images are released. I've recently noticed that with searxng (using redis as db), hosted through nginx proxy manager, will have a steady downtime of about 15mins post update then come back online. This is extremely frequent for searxng's case as I have watchtower run every day and my preferred way of running most of my containers is with the latest tag. The way out of this downtime in my experience is a restart of NPM which brings back the searxng service. I'm looking for a way to automate a restart of the NPM container after a successful update of searxng's container. I have checked the docs for watchtower, and the lifecycle hooks (a way to run sh scripts pre/post update) are able to run only from the applied container and not from the host system.
fedilink