Skip Navigation

Posts
8
Comments
253
Joined
2 yr. ago

  • I wrote this ansible role to setup dovecot IMAP server. Once a year I move all mail from the previous year from various mailboxes to my dovecot server (using thunderbird).

  • Nice! I suggest adding a link to in in the README

  •  bash
        
    wget --continue --timestamping --show-progress https://tails.boum.org/tails-signing.key
    wget --continue --timestamping --show-progress https://tails.boum.org/torrents/files/tails-amd64-6.8.1.iso.sig
    gpg --import "tails-signing.key"
    wget --continue --timestamping --show-progress https://mirrors.wikimedia.org/tails/stable/tails-amd64-6.8.1/tails-amd64-6.8.1.img
    gpg --keyid-format 0xlong --verify tails-amd64-6.8.1.iso.sig tails-amd64-6.8.1.img
    
      

    (adapted from my script https://gitlab.com/nodiscc/distrib-dl / https://github.com/nodiscc/distrib-dl)

  • I think any kind of graphical application should have at least one screenshot linked in documentation/README

  • Interesting post, but what does this have to do with selfhosting? This is not /c/llm

  • I do this with https://www.sphinx-doc.org/ + a basic Makefile and config file to make it a bit nicer. I will publish my template a bit later and report back.

  • I wrote this ansible role to setup dovecot IMAP server. Once a year I move all mail from the previous year from various mailboxes to my dovecot server (using thunderbird).

  • I use the Netdata agent (with cloud features disabled). Easy installation, FOSS, 0 configuration required, tons of metrics.

  • I wrote my own ansible role to deploy/maintain a matrix server and a few goodies (element/synapse-admin). If you're not using ansible you should still be able to understand the deployment logic by starting at tasks/main.yml and following includes/tasks from there.

  • host maps

    It does require a beefy server (rendering tiles is CPU/RAM-intensive, storing pre-rendered tiles is expensive on storage) It should be doable on limited hardware if only a small area.

    I think the better move would be keeping/distributing a local copy of the OsmAnd android APK and a few maps for the app. Because you'll not be able to provide map access to people from your server if the Internet/local fiber/phone network is down - this way everyone can have their own full copy of the map.

    I'm not sure about the method to extract map data from the app storage directory though.

  • Just download a copy of a recent wikipedia dump. You can open it in the Kiwix desktop application (work fine even on an old laptop), the android app (though I've never tried opening a full 100GB dump with a phone, not sure if it would work well), or install the kiwix-tool package and serve the .zim file with kiwix-serve (https://wiki.kiwix.org/wiki/Kiwix-serve). You'd also probably want a reverse proxy/usual basic web server/security setup around that.

  • Second this, always have a device preloaded with Kiwix and one of the wikipedia dumps. A new vesrion is uploaded every few (~6 months). The full English wikipedia dump with images (low-res versions only though) is only 103GB.

    • ansible playbook for automated/self-documenting setup
    • for one-off bugs or ongoing/long-term problems, open an issue on my gitea instnce and track the investigations and solutions there.