Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)LE
Posts
10
Comments
436
Joined
2 yr. ago

  • Maybe 1 hr every month or two to update things.

    Thinks like my opnsense router are best updated when no one else is using the network.

    The docker containers I like to update manually after checking the release logs. Doesn't take long and I often find out about cool new features perusing the release notes.

    Projects will sometimes have major updates that break things and I strongly prefer having everything super stable until I have time to sit down and update.

    11 stacks, 30+ containers. Borg backups runs automatically to various repositories. Zfs auto snap snot also runs automatically to create rapid backups.

    I use unraid as a nas and proxmox for dockers and VMs.

  • I moved form next cloud to seafile. The file sync is so much better than next cloud and own cloud.

    It has a normal windows client and also a mount type client (seadrive) which is also amazing for large libraries.

    I have mine setup with oAuth via Authentik and it works super well.

  • It's not unusual for an update to have breaking changes that require some manual intervention to fix.

    If you are on latest, it can also be hard to know which version you used to be on if you want to roll back.

    For important things, I used specific version tags and then check the release notes before upgrading.

  • Mainly because of the number of things I have that I rely on every day and definitely don't want to break until I'm ready to upgrade it and have time to fix it if it does break.

    I know many do use :latest but having a service break while I'm away or travelling really sucks

  • Who was pulling the dicker compose and just straight up running the GitHub version on their server. That seems crazy. Even pulling :latest tag seems crazy to me but this is another level.

    This change is only breaking if you are running someone else's docker compose on your server without looking at it.

    Also who was running their entire photo album in a docker volume rather than a mount point on the host. Another insane decision. To be fair, the default docker compose never should have had that. It should have been a mount point right from the start.

  • For others, beware that in a docker, each plugin needs its own docker container.

    I run everything in docker except for HA which I run in a VM (HaOS) which makes it super easy to use.

    Edit: by plugins I meant add-ons

  • Is this a fresh install? Why is there any debugging? To just connect with an ip requires no config files at all.

    I only changed 1 config file add the crfs URL and also added some lines for oAuth. No config file changes are needed by default. It's all docker compose

  • It does allow you to found the files, just not via smb or ftp. It requires it's own filesystem but works very well.

    https://manual.seafile.com/extension/fuse/

    I've tested this on my backups for which I use borg backup.

    First I mount a remote borg repository using one command. Then mount the seafile repository via the fuse command above.

    Note that the sea drive client app does the same thing as above but in the gui and mounts the library as a virtual hard drive.

    https://help.seafile.com/drive_client/drive_client_for_win10/

    This is different than the actual seafile client app which is the standard folder sync / Dropbox like behavior that most users will only ever use. All the other things I mentioned above are for advanced use cases only and not normally needed but very nice to have.

    BTW authentik for Single sign on works super well