I use it for Home Assistant and ntfy in combination with Caddy. Certificates are managed by Vaultls (https://github.com/7ritn/VaulTLS) which makes it quite easy to setup and use on new devices.
@lemmy.world
I use it for Home Assistant and ntfy in combination with Caddy. Certificates are managed by Vaultls (https://github.com/7ritn/VaulTLS) which makes it quite easy to setup and use on new devices.
VaulTLS: https://github.com/7ritn/VaulTLS
Wiki.js is pretty simple and the solution I settled for after testing multiple options. Other examples can be found here: awesome-selfhosted
Currently, I’m just using my root account with Docker and update everything manually. I have dockcheck-web installed to check whether any updates are available (https://github.com/Palleri/DCW). From the outside everything is only accessible using Wireguard and connections have to go through a Caddy proxy in order to reach a container. Curious what other peoples setup is.
I’m using Nextcloud to sync my photos and use the read-only feature of Immich which works really well. I have a cronjob to automatically sync the latest photos into Immich over night which also works quite nicely.
I’m currently using Piraeus / LINSTOR and am quite happy with it: https://github.com/piraeusdatastore/piraeus
I’m using this since last week and it works great so far. I only have one issue where some photos in my timeline are incorrectly placed at a wrong date, but this is a known issue and should be fixed soon.
You could look into mutual TLS / mTLS to protect your instance. You will need to set this up using a reverse proxy at your server (like Caddy) and then add a client certificate to your user devices. If you use the Immich app, I think it also supports adding this certificate under Settings -> Advanced -> SSL Client Certificate. Here you can find a tutorial on how to set it up: https://www.apalrd.net/posts/2024/network_mtls/
(Edit: you will need to ensure that all clients who want to receive your shared photos have a client certificate installed, so depending on the number of clients this might be okay or less useful)
In theory the database can end up in an invalid state when you leave the database container running. What I do for most containers is to temporarily stop them, backup the Docker volume and then restart the container.
It is in the diagram I think: “Excalidraw”
Also never heard of it and always nice to find new FOSS.
I can confirm that the resource usage is quite low indeed. I only used it with Nomad instead of Kubernetes, so I can’t comment on how to best migrate PVs and PVCs.
I had similar issues with memories, so that’s why I switched to Immich last week. So currently I still sync using Nextcloud to a specific directory and then use the read-only functionality of Immich. I also used Photoview for a period of time which also works quite nice, but the app gets updated less often than Immich’s app and also has less functionality. In the end I hope to completely move to Immich when syncing works both ways.
thanks for using Leebra!
go to feed...