• 4 Posts
  • 107 Comments
Joined 1 year ago
cake
Cake day: June 9th, 2023

help-circle


  • Vaultwarden itself is actually one of the easiest docker apps to deploy…if you already have the foundation of your home lab setup correctly.

    The foundation has a steep learning curve.

    Domain name, dynamic DNS update, port forwarding, reverse proxy. Not easy to get all this working perfectly but once it does you can use the same foundation to install any app. If you already had the foundation working, additional apps take only a few minutes.

    Want ebooks? Calibre takes 10 mins. Want link archiving? Linkwarden takes 10 mins

    And on and on

    The foundation of your server makes a huge difference. Well worth getting it right at the start and then building on it.

    I use this setup: https://youtu.be/liV3c9m_OX8

    Local only websites that use https (Vaultwarden) and then external websites that also use https (jellyfin).



  • I’ve got multiple apps using LDAP, oauth, and proxy on authentik, I’ve not had this happen.

    I also use traefik as reverse proxy.

    I didn’t manually create an outpost. Not sure what advantage there is unless you have a huge organization and run multiple redundant containers. Regardless there might be some bug here because I otherwise have the same setup as you.

    I would definitely try uploading everything to the latest container version first


  • Does anyone know if dockge allows you to directly connect to a git repo to pull compose files?

    This is what I like most about portainer. I work in the compose files from an IDE and the check them into my self hosted git repo.

    Then on portainer, the stack is connected to the repo so only press a button to pull the latest compose and there is a check box to decide if I want the docker image to update or not.

    Works really well and makes it very easy to roll back if needed.


  • I don’t remember all the details. They never went closed source, there was a difference in opinion between primary devs on the direction the project should take.

    Its possible that was related to corporate funding but I don’t know that.

    Regardless it was a fork where some devs stayed with owncloud and most went with NextCloud. I moved to NextCloud at this time as well.

    OwnCloud now seems to have the resources to completely rewrite it from the ground up which seems like a great thing.

    If the devs have a disagreement again then the code can just be forked again AFAIK just like any other open source project.













  • I use zfs so not sure about others but I thought all cow file systems have deduplication already? Zfs has it turned on by default. Why make your own file deduplication system instead of just using a zfs filesystem and letting that do the work for you?

    Snapshots are also extremely efficient on cow filesystems like zfs as they only store the diff between the previous state and the current one so taking a snapshot every 5 mins is not a big deal for my homelab.

    I can easily explore any of the snapshots and pull any file from and of the snapshots.

    I’m not trying to shit on your project, just trying to understand its usecase since it seems to me ZFS provides all the benefits already