• 5 Posts
  • 120 Comments
Joined 2 years ago
Cake day: July 3rd, 2023
  • tofubl@discuss.tchncs.detoSelfhosted@lemmy.world•Any nice playbook or tutorial to host a static website from home?English
    3·
    5 days ago

    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.

  • tofubl@discuss.tchncs.detoSelfhosted@lemmy.world•What hardware do you use for Nextcloud?English
    3·
    6 days ago

    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.

  • tofubl@discuss.tchncs.detoSelfhosted@lemmy.world•Recommendation Self Hosting BlogEnglish
    1·
    6 days ago

    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.

  • tofubl@discuss.tchncs.detoSelfhosted@lemmy.world•Need some help setting up gethomepage in my serverEnglish
    1·
    11 days ago

    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]
    }