• 1 Post
  • 23 Comments
Joined 3 years ago
cake
Cake day: June 7th, 2023

help-circle


  • Forward thinking venture capital funded companies are getting rarer, hence the question on motivation. Especially the last few years many VC Foss companies have squeezed harder the other way (gitea, Terraform, docker). So all kudos to BitWarden for launching Lite.

    What you say a about brand dominance, or brand protection makes a lot of sense. It’s not a good look for them that a large number of people choose to use an unofficial implementation instead of theirs. And should there ever be a catastrophic security issue with Vaultwarden, it would still reflect bad on BitWarden as that kind of nuance (like “unofficial server side implementation”) tend to get lost in reporting. Having more IT workers self-host official version probably also helps pave the way for bringing enterprise-bitwarden to companies.

    Valve are a bit of a unicorn though, because they are privately owned. There’s no investors demanding ROI the next quarter, which gives them freedom to think long term.
    When Microsoft launched windows8 and the Microsoft Store, Valve took that as an existential threat to their whole business model (the Steam store). Valve feared that Microsoft was trying to position itself like Apple on iOS and Google on Android, where there is only one platform store, and all apps are purchased through the platform store, and the platform store takes that sweet sweet 30% cut. So Valve pivoted to ensure the Steam store would not be obsolete, and give customers a reason to still use the Steam store. And what they achieved is awesome, for Linux, for Valve and for gamers. But it took nearly a decade, which is a level of patience few companies have.





  • Hardest issue would probably be financing, and motivation.

    GPUs are expensive, electricity is expensive. All the current major LLMs are huge loss leaders for giant players with deep pockets. A distributed AI service would be by smaller players without the financing nor the motivation to upfront all the cost.

    There is “folding@home” where you donate time on your hardware for scientific calculations, but that’s quite different from donating time on your hardware to some random unknown stranger to generate AI cat images or summarise a news article.

    Lemmy and Mastodon etc have a comparatively modest monetary (and energy/environmental) cost, and the benefit is building communities and bringing people together. For distributed AI the cost ( monetary and energy/environmental) is higher, and the benefit is limited.


  • Can attest that Folder Sync is excellent. I use it all day (in the background) for two-way sync (notes) and backup of photos videos etc

    Though a small PSA on setting up:
    I once set up a new share on a new phone with two-way sync, and the app decided to sync the (newer) empty directory to the server (i.e. delete everything) instead of pulling the files from the server to the phone.
    Easy fix: Restore notes from backup (step 0: have backups in the first place), then do an initial 1-way sync from server to phone, then change the sync job to two-way.



  • I highly recommend you use Proxmox as the base OS. Proxmox makes it easy to spin up virtual machines, and easy to back up and revert to backups. So you’re free to play around and try stupid stuff. If you break something in your VM, just restore a backup.

    In addition to virtual machines, Proxmox also does “LXC containers” , which are system level containers. They are basically a very light weight virtual machine, with some caveats like running the same kernel as the host.

    Most self-hosting software is released as a docker-image. Docker is application level containers, meaning only the bare minimum to run the application is included. You don’t enter a docker container to update packages, instead you pull down a new version of the image from the author.

    There are 3 ways to run docker on Proxmox:

    • Install docker inside a virtual machine (recommended).
    • Install docker inside a LXC Containers (not recommended because of various edge cases)
    • Install docker directly on the Proxmox host (not recommended for various reasons).
    • (There is ongoing work for running docker images directly in Proxmox, this is in beta/preview since Proxmox 9.1).

    The “overhead” of running docker inside a VM on the host is so negligible, you don’t need to worry about it.


  • I had never heard of dockge before, but this sounds like the killer feature for me:

    File based structure - Dockge won’t kidnap your compose files, they are stored on your drive as usual. You can interact with them using normal docker compose commands

    Does that mean I can just point it at my existing docker compose files?
    My current layout is a folder for each service/stack , which contains docker-compose.yaml + data-folders etc for the service. docker-compose and related config files are versioned in git.
    I have portainer, but rarely use it , and won’t let it manage the configuration, because that interfered with versioning the config in git.



  • I’m using NixOS with KDE for HTPC, though I’m not sure I’d recommend it unless you’re eager to learn Nix.

    The upshot is that it’s super stable, and everything is declared and versioned in the git repo, including my lirc device codes and node-red automation flow for lirc and mqtt. (The HTPC shows up as a mqtt switch in home assistant for turning on and off, and the HTPC turns on or off the TV and amplifier through IR as the PC turns on or off)

    I mostly use Firefox and various streaming sites for video, and Spotify desktop client for music. A gyro mouse/keyboard is the main input device, plus wireless Xbox360 controllers for streaming games with Moonlight (from Flathub)




  • Thanks for sharing! TIL about autofs. Now I’m curious to try NFS again.

    What’s the failure mode if the NFS happens to be offline when PBS initiates a backup? Does PNS try to backup anyway? What if the NFS is offline while PBS boots?

    EDIT: What was the reason for bind mounting the NFS share via the host to the container, and NFS mounting from NAS to host?
    I did the NFS-mount directly in the PBS. (But I am running my PBS as a VM, so had to do it that way)


  • I run PBS as a virtual machine on Proxmox, with a dedicated physical harddrive passed through to PBS for the data.

    While this protects from software failures of my VMs, it does not protect from catastrophic hardware failure. In theory I should be able to take the dedicated harddrive out and put it in any other system running a fresh PBS, but I have not tested this.

    I tried running the same PBS with an external NFS share, but had speed and stability issue, mainly due to the hardware of the NFS host. And I wasn’t aware of autofs at the time, so the NFS share stayed disconnected