• 5 Posts
  • 114 Comments
Joined 2 years ago
cake
Cake day: July 3rd, 2023

help-circle


  • “Just” some highly specific VM settings, in the end. I don’t know much about that, and terms like qemu don’t mean anything to me so I followed blog posts until it worked. (This one and maybe this one, I think.) It’s possible that it is actually trivial.

    It’s been a while, but I can look up what I have when you need it. Feel free to ping me!

    Yes, it was exactly that: Once I got the NICs set up the way I wanted them it was a breeze and everything just works. And I really like that I made every part work myself, no magic. I learned a lot, and wouldn’t have had I relied on Proxmox fiddling with the right parts for me.


  • I was in a similar spot not too long ago, setting up a firewall and general network box. I was going to go with Proxmox but a fellow Lemmy guy strongly advocated for Incus on top of vanilla Debian. I was intrigued and ended up going for it. Learned a lot about networking with systemd (bridging, IP assignment and so on) for things I could have gotten for free in Proxmox (literally a few clicks), and had to fight Incus to work with a FreeBSD VM for Opnsense, but I love the setup now. Pure debian with a few Incus VMs and Docker inside of those as needed. So clean!








  • You can set up your project in a private repo and in your deploy action push it to the main branch of your public Pages repo. I agree it’s not a huge deal to show the source, but I prefer it like that.

    name: Deploy Hugo site to Github Pages
    
    on:
      push:
        branches:
          - main
        workflow_dispatch:
    
    jobs:
      build:
        runs-on: ubuntu-latest
    
        steps:
          - name: Checkout repository
            uses: actions/checkout@v4
    
          - name: Set up Hugo
            uses: peaceiris/actions-hugo@v3
            with:
              hugo-version: "0.119.0"
              extended: true
    
          - name: Build
            run: hugo --minify
    
          - name: Configure Git
            run: |
              git config --global user.email "you@example.com"
              git config --global user.name "Your Name"
          - name: Deploy to GitHub Pages
            env:
              GITHUB_TOKEN: ${{ secrets.DEPLOY_TOKEN }}
            run: |
              cd public
              git init
              git remote add origin https://user/:${{ secrets.DEPLOY_TOKEN }}@github.com/USER/USER.github.io.git
              git checkout -b main
              git add .
              git commit -m "Deploy site"
              git push -f origin main
    

    edit: Markdown is adding a / after “user” in above git remote command. Don’t know how to get rid of it.


  • My Nextcloud journey went from a Raspberry Pi 2B with a single USB HDD over a Pi 3B to a QNAP 2bay NAS on RAID 1 with a proper backup strategy including daily encrypted cloud backup. Having come to rely on the setup much more than when I was starting out playing with it years ago, I sleep much easier now. That said, I never lost any data, even on very questionable hardware without any redundancy whatsoever.


  • If you’re not very set on hosting at home, hosting a static Hugo page directly on Github Pages is incredibly convenient and easy (and free.) With the right Github Action, updating the site is as simple as pushing content to the main branch and it automatically deploys. And should Github ever give you a reason to do so, moving away is as simple as copying your static files to any other webhost and pointing your domain there instead.

    Edit: It’s of course equally easy to deploy on your NAS - just a basic nginx serving the directory with your static site that Hugo generated.




  • Would love to see it.

    Here’s mine from the Paperless compose.yml (non functional):

      webserver:
        image: ghcr.io/paperless-ngx/paperless-ngx
        [...]
        labels:
          - homepage.group=Productivity
          - homepage.name=Paperless
          - homepage.icon=paperless.png
          - homepage.href=https://[LOCAL URL]
          - homepage.description=Document Management
          - homepage.widget.type=paperlessngx
          - homepage.widget.url=http://[PAPERLESS IP:PORT]
          - homepage.widget.key=[PAPERLESS API TOKEN]
    

    And here’s the error from Homepage frontend:

        API Error: Unknown error
        URL: http://[PAPERLESS IP:PORT]/api/statistics/?format=json
        Raw Error:
        {
            "errno": -110,
            "code": "ETIMEDOUT",
            "syscall": "connect",
            "address": "[PAPERLESS IP]",
            "port": [PAPERLESS PORT]
        }
    




  • A virtual environment is just a copy of the python and pip binaries. When you activate the venv, the venv dirs temporarily get added to your path, so your regular python alias points to the binary in the venv (run which python with venv active to verify). Pip will install modules to a subdir of your venv. It basically works like npm and the node_modules dir.