what is a good solution that does incremental backups of docker volumes? o btrfs subvolumes… i have them mapped

very cool, are you planning an android app?

how this compare with https://github.com/Stirling-Tools/Stirling-PDF ?

i have this hosted, should i switch?

here is my deploy:

https://github.com/simone-viozzi/my-server/blob/main/ocis_wopi/docker-compose.yml

be aware that i’m a couple of versions behind because there are breaking changes with no upgrade path. so i need to restart from scratch… and that’s annoying.

i use trefik as a reverse proxy, and a subdomain for each service.

i like to have them separated by service, i have 3/4 dbs running, at least 2 of them are postgreSQL.

i’m using it at work to take notes and write documentation.

i think it’s a fantastic app.

i have it as a pwa and have at least one silverbullet for each desktop.

i have ~100 notes perfectly organized in silverbullet!

the only things i would change is compatability with other tools. there is no way to export to PDF, if you nees to convert the note to docx you need to copy paste everything.

you can install it as a PWA

Hi i like your project and i will most likely start to use it.

i also use silverbullet.md, it could be awesome to have some kind of interoperability from the two.

arch + docker for the services

how does this compare with silverbullet?

can i link pages? do queries?

you could use btrfs snapshots of the volumes you want to preserve. then send the snapshot to a remote location.

if the ssd fries you just need to download the snapshots and restore their layout.

i have a script for it and i use it on my server: https://github.com/simone-viozzi/btrfs2cloud-backup

immich is the way to go

i have been running the new owncloud (ocis) and, with some quirks and very basic functionality, it’s been running for 2+ years and survived multiple updates without major complications

you should exclude the immich stack from auto-updating and subscribe to immich releases.

most of the time will just be a docker compose pull && docker compose up -d && docker compose logs -f

maybe is specific to my country, but here the majority of network plans have a CGNAT down the line. So we have a private ip at the router and there is no way to reach it, unless you reley the traffic to a third point.

if you want a public ip (even dynamic) you need to pay up

this is a great idea but it will only work if they have a public ip

this is a long shot but the keycloack container is connected to 2 networks, does this couse a problem?

i’m saying this because traefik need you to specify on the labels which docker network it should use. maybe there is something similar.

but as i said this is a very long shot and it’s probably bs

yes is the same, or at least should.