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

help-circle
  • There’s also situations where you want the computer to be truly off (without loosing your open documents etc), to the point where you can take out the battery and it’s no big deal.

    Also, for work my fancy new computer has fancy new “modern suspend”, which isn’t actually suspend at all. The fan is still spinning and it’s generating lots of heat. Not great in backpacks and certainly not great in industrial field work where there are areas where non rated powered electronics are not allowed due to potential explosive atmosphere.

    Meanwhile hibernate is still hibernate. The computer is actually fully powered down.







  • If you’re already using node-red, the Wake On Lan node works well, and with node-red it’s easy to trigger the magic packet based on whatever trigger condition you want.

    The only limitation I know is WOL doesn’t work after a power outage, because the switch and RPI doesn’t know where to find the target machine

    Thanks for the tips on reusable enterprise cards btw






  • 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.





  • 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.