{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreibeqgsd3x645rudlm7z4fkvkqqrsyr43mov52lfd3d7jwbvpbypl4",
    "uri": "at://did:plc:3dfgnbyx3tgud2iqvwduxbcw/app.bsky.feed.post/3ml7qg4eldme2"
  },
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreifrj7anahfbq2uj6lzwbzuveco67fv4tybz5tfogkro46q7qfs4he"
    },
    "mimeType": "image/png",
    "size": 33833
  },
  "path": "/article.php?id=2026-05-06_self-hosted-forgejo-instance",
  "publishedAt": "2026-05-06T08:46:31.000Z",
  "site": "https://dmpop.xyz",
  "tags": [
    "Codeberg",
    "Forgejo",
    "Gitea"
  ],
  "textContent": "I host my open-source projects on Codeberg. But out of respect for this excellent service, I don't want to clutter it with one-off piles of code and stuff I don't take seriously. Also, I wanted to have my own \"incubator\" where I let my half-baked code sit until it matures into something usable before I share it on Codeberg. Long story short, I deployed a self-hosted Forgejo (a fork of Gitea) instance on my own server.",
  "title": "TIL: Deploying a self-hosted instance of Forgejo (aka Gitea) is easier than I thought"
}