@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.
@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.
@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?
@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
@ErwinLottemann@Solvena ..or take it one step further and store your private key, only(except your offline backup), on an hsm/smartcard such as; yubikey.
@Moonrise2473@cybersandwich I both agree and disagree... but always use named volumes. Easier to manage/monitor your volumes then use an <backup-container>, maybe rclone, that shares the same volume and sends the data to some safe place
or, if you still prefer, in your named volume section tell docker to use a custom path.
@SmallAlmond I don't know much about streamio, but I noticed this on their webpage;
"There is also a Guest mode at signup, which requires no data whatsoever: in this mode, no calls are made to our backend. However, it comes at the expense of useful features, such as being able to sync your library across devices."
@olof I don't know, but heard Kraken is good. Found this blog talking about MiCA, might be good to look after: https://bitcourier.co.uk/blog/best-crypto-exchanges-europe unless you do crypto to move away from centralised banking.
@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.
@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
@KelsonV You 'could' do "ssh nextcloudserver -l www-data php occ list", if you allow interactive login with your webserver user.
@KelsonV I think davfs would be the lighter interface to nextcloud.
@clb92 @Appoxo ...but traefik's autoconfigure from labels on your services in the compose file is so nice.
@ErwinLottemann @Solvena ..or take it one step further and store your private key, only(except your offline backup), on an hsm/smartcard such as; yubikey.
@Moonrise2473 @cybersandwich I both agree and disagree... but always use named volumes. Easier to manage/monitor your volumes then use an <backup-container>, maybe rclone, that shares the same volume and sends the data to some safe place
or, if you still prefer, in your named volume section tell docker to use a custom path.
volumes:
myvolume:
driver: local
driver_opts:
type: none
o: bind
device: /host/path/to/volume
@SmallAlmond I don't know much about streamio, but I noticed this on their webpage;
"There is also a Guest mode at signup, which requires no data whatsoever: in this mode, no calls are made to our backend. However, it comes at the expense of useful features, such as being able to sync your library across devices."
🤔