itmike

@alvaro @selfhosted @selfhost keepassxc perhaps.

@originalucifer @ozoned hm.. Why do you call it blog then? It's just someone's web page with text, pictures and video published to it. Languages evolves and new words can describe new implementations better.

@kristoff Multicloud deployments is a thing, but far from common practice, I believe.

@kristoff If you can do a test restore on new instance with a restored db from your back up, I say you are good to go.. maybe you can benefit from restoring some cache as well but that shouldn't be required imo. Test your back up and document your restore process!

@Appoxo @ShortN0te On your own network you should be able to have a long enought lease that it shouldn't be a problem if your dhcp server is unavailable sometimes.

@bort @ijeff As long as you don't root it, yes... and if you root it there is workarounds that might work.

@erlend_sh Interesting... will give this a try..

@Tywele https://www.tarsnap.com/

@AdmiralShat @Kushan It's federated right? so you don't need to leave, just move on to a different federated server in the network.. or am I missing something?

@PlutoniumAcid @spudwart Did you configure memcache and nextclouds scheduled maintenance job, both are very much needed for nextcloud to work good.

@ErwinLottemann I like named volumes in my compose files better thou, keep them organised under the volume section and manageable with docker-cli if needed.

@Pete90 There is plugins you can use to tell docker where your volumes are. Something like this works for local directories:

Docker will create a _data directory as usual.

volumes:
web_data:
db_data:
driver: local # Define the driver and options under the volume name
driver_opts:
type: none
device: /data/myservice/db_data
o: bind