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/)KL
Posts
4
Comments
241
Joined
2 yr. ago
  • I haven't seen it mentioned here, so just an FIY: Linux Mint is a "regular" distro, while Bazzite is an immutable distro, meaning the root filesystem is read-only.

    That means a lot of the "normal" ways of doing stuff you find online will need to be done differently. For example installing system level packages requires a reboot, to boot in to the new "system image". If something gets booked you can reboot in to an old system image to recover. Regular desktop (Flatpak) apps can be installed without rebooting.

    Bazzite is based on Fedora, and very similar to Fedora SilverBlue (immutable version). So if you can't find answers when looking online "how to do X in Bazzite" try instead "how to do X in SilverBlue".

    And FYI Linux Mint comes with an easy to use app Timeshift for system level backup and restore (by default it does not backup your documents etc in your HOME folder). Very handy to recover from a borked update or installing something you shouldn't have.

  • SingleFile provides a faithful representation of the original webpage, so bloated webpages are indeed saved as bloated html files.

    On the plus side you're getting an exact copy, but on the downside an exact copy may not be necessary and takes a huge amount of space.

  • SingleFile is a browser addon to save a complete web page into a single HTML file. SingleFile is a Web Extension (and a CLI tool) compatible with Chrome, Firefox (Desktop and Mobile), Microsoft Edge, Safari, Vivaldi, Brave, Waterfox, Yandex browser, and Opera.

    SingleFile can also be integrated with bookmark managers hoarder and linkding browser extensions. So your browser does the capture, which means you are already logged in, have dismissed the cookie banner, solved the capthas or whatever else annoyance is on the webpage.

    ArchiveBox and I believe also Linkwarden use SingleFile (but as CLI from the server side) to capture web pages, as well as other tools and formats. This works well for simple/straightforward web pages, but not for annoying we pages with cookie banners, capthas, and other popups.

  • Reading your post again, you should start by moving your docker management from CasaOS to vanilla docker-compose files, and keep them in a git repo.

    I still think you definitely should look in to NixOS and what it can offer, cause it seems like that is where your mindset is going.

    But NixOS is a drastic change, you should start by just converting your individual services one by one from CasaOS management to docker-compose files. One compose file for all services is possible, but I would recommend one compose file for each service. Later you can move from Debian to NixOS while using the same docker-compose files.

  • I would like to have a system when I know what I did, what is opened/installed/activated and what is not

    You sound like you need to to look in to Nix and NixOS. The TLDR is that everything is declared in a configuration file(s), which you can and should back up in git. The config files tell you exactly what you did , and the config file comments together with git commit history tell you why.

    The whole system is built from this configuration file. Rollback is trivially easy, either by rebooting and selecting an older build during the boot manager, or reverting to an older git commit and rebuilding (no reboot required, so usually faster)

    Now fair warning, Nix (and NixOS) is a big topic, very different from normal way of thinking about software distribution and OS. Nix is not for everyone.

    You should also at the very least have a git repo for docker-compose files for your services. Again, that will declaratively tell you what you did and why.

    Also, if NixOS is too extreme, you should also look in to declarative management tools like Ansible etc

  • Hard to say without knowing which method you used to install HomeAssistant.

    But I never found mdns .local addresses to be very reliable. They work 80-90% of the time, but the remaining 10-20% are a hassle.

    Instead I'd recommend you install PiHole (in a docker container is easiest). PiHole is a DNS server intended for network-level ad-blocking. But it also have a handy feature of defining local DNS entries, so you can have HomeAssistant.myhome or HomeAssistant.whatever (.local should not be used with PiHole local DNS because .local is meant for mdns)

  • Not Op, but I was in a very similar situation (decent pay, old house, old car, not many fancy purchases). While many people here will borrow a lot and pay the minimum on their mortgage, I paid down my mortgage completely. (and otherwise spent money on travel).

    Ironically, this is bad financial advice. The last 15-20 years interest have been very low, and house prices have soared. It would make much more financial sense to borrow more and buy a nicer house. But I value the freedom I get from not having a mortgage. And I never borrowed to buy a car, as cars depreciate like rocks

  • Some key points regarding Proxmox:

    • Even if you only want to run two services, you still want to keep them isolated. This can save you much pain and frustration in the future when they require upgrades
    • Proxmox let's you easily manage VM and LXC containers. So you can easily manage backups, or spinning up a separate test instance of your service. Which again, can save you pain and frustration when it comes to future updates of your services.
    • Backups are even better if you can deploy the separate Proxmox Backup Server
    • Should you ever want to add another service in the future, you can test it out in a new VM or container without it affecting your existing services at all
    • ZFS is indeed quite memory hungry, but AFAIK it's mainly used for the read cache, and can be tuned to use less RAM at the cost of performance
    • ZFS is mentioned a lot because it's good, but Proxmox also supports a range of other storage technologies: LVM, mdraid, EXT4, CEPH
    • Proxmox is just standard Debian and KVM/QEMU virtual machines under the hood. Which means you can use standard tooling and workflow should you need it for some edgecase.
    • You mentioned Jellyfin in a container: My understanding is that Jellyfin in Docker has some extra limitations or complexities when it comes to hardware encoding.
      • Jellyfin also has official documentation for how to deploy in LXC container and get HW transcoding working (Less complex than in Docker).
      • LXC containers are not like Docker containers. While a Docker container is meant to be an immutable image of a (single) application, LXC is more like a full fledged VM, but without the overhead of virtualization. LXC containers are full systems, and you install software via the usual apt, dnf etc
      • The "correct" way to run Docker in Proxmox is to run Docker in a Virtual machine. Installing Docker inside a LXC container is also possible, with some caveats. Installing Docker directly on the Proxmox host is not recommended

    For reference, my oldest Proxmox server is a 2013 AMD dualcore 16GB DDR2 ram with VMs on LVMthin on a single SSD, with legacy VM doing mdraid of 3 HDDs using hardware passthrough. Performance is still OK, the overhead from Proxmox is negligible compared to strain from the actual workloads

  • On Windows the system wakes up when connected or disconnected from an AC adapter.

    Does it? I could sweat my work laptop (windows 10) doesn't , and I'm pretty sure I'd notice cause I sleep and move it a lot during a working day.

    Is it a windows 11 thing? Or something to do with the so-called "hybrid sleep / hybrid boot"? (Pretty sure that's disabled by corporate, and for friends and family I always disable that when their laptop goes in a boot crash loop). Does BitLocker matter ?

  • Selfhosted @lemmy.world
    klangcola @reddthat.com

    Why use Named volume vs Anonymous volume in Docker?

    What are the pros and cons of using Named vs Anonymous volumes in Docker for self-hosting?

    I've always used "regular" Anonymous volumes, and that's what is usually in official docker-compose.yml examples for various apps:

     yaml
        
    volumes:
      - ./myAppDataFolder:/data
    
    
      

    where myAppDataFolder/ is in the same folder as the docker-compose.yml file.

    As a self-hoster I find this neat and tidy; my docker folder has a subfolder for each app. Each app folder has a docker-compose.yml, .env and one or more data-folders. I version-control the compose files, and back up the data folders.

    However some apps have docker-compose.yml examples using named volumes:

     yaml
        
    services:
      mealie:
        volumes:
          - mealie-data:/app/data/
    volumes:
      mealie-data:
    
    
      

    I had to google documentation https://docs.docker.com/engine/storage/volumes/ to find that the volume is actually called mealie_mealie-data

     shell
        
    $ docker volume ls
    DRIVER    VOLUME NAME
    ...
    local     mealie_mealie-data
    
    
      
    Deep Rock Galactic @lemmy.world
    klangcola @reddthat.com

    YouTuber Smii7y discovers the way of Rock and Stone

    The joys of discovering DRG for the first time and gleefully learning all the mechanics. Extra props for the careful and methodical test to verify if the game has Friendly Fire

    Lemmy Support @lemmy.ml
    klangcola @reddthat.com

    Downvoting disabled, federated voting

    Some instances disable downvoting. Is this intended to be for communities on that instance or users on that instance, or both?

    I noticed while reading Memes@lemmy.ml ( https://reddthat.com/post/2053 ) that some commenters were talking about being downvoted, but I have no downvote button. Because downvoting is disabled on my instance?

    How does it work the opposite way? Are users from lemmy.ml allowed to downvote on posts for example beehaw (who also has disabled downvoting)

    Lemmy Support @lemmy.ml
    klangcola @reddthat.com

    How does "language" selection work in Lemmy?

    Many instances say to keep language settings as "undetermined" otherwise you won't see most posts Example: https://lemmy.blahaj.zone/post/59161 Example: https://reddthat.com/settings

    Yet when I try to post a comment it will fail with language_not_allowed because initially there is no language selected. So I need to click on the "Select language" drop-down and choose English (the only option)

    Actually in the Lemmy web interface (at least on my instance reddthat.com) the Post button will spin endlessly with no indication of what's wrong. Using the Jerboa Android app there's is the very brief error message language_not_allowed, and the comment disappears so I have to type it out again! On the Jerboa app there's also no option to select the language for the comment, so I can't use it to comment at all.

    I experienced this language_not_allowed error while commentating on gaming@beehaw.org and lemmy_support@lemmy.ml , both English language communities

    So how is this language setting supp