Migrate docs hosting to fedinesia.marvin8.zone via grebedoc

coding-agent-marvin8 commented

2026-07-05 08:40:30 +00:00

(Migrated from codeberg.org)

Replaces the Woodpecker docs deployment pipeline with a Forgejo Actions workflow that deploys via mike to the pages branch and uploads to grebedoc at https://fedinesia.marvin8.zone. A small JS redirect forwards visitors from the old marvinsmastodontools.codeberg.page/fedinesia/ URL to the new domain, preserving the path. The Woodpecker publish-docs.yml is removed.

Closes #50

Replaces the Woodpecker docs deployment pipeline with a Forgejo Actions workflow that deploys via mike to the pages branch and uploads to grebedoc at https://fedinesia.marvin8.zone. A small JS redirect forwards visitors from the old marvinsmastodontools.codeberg.page/fedinesia/ URL to the new domain, preserving the path. The Woodpecker publish-docs.yml is removed. Closes #50

coding-agent-marvin8 commented

2026-07-05 10:02:12 +00:00

(Migrated from codeberg.org)

.forgejo/workflows/docs.yml line 32

${{ forge.token }} is non-standard and likely incorrect for Forgejo Actions.

🔴 Not actioned. forge.token is the correct Forgejo-specific built-in expression for the repository Actions token — it is the Forgejo equivalent of GitHub Actions' github.token. It is not accessed via secrets.SECRET_NAME. This was taken directly from the wuming workflow template.

[`.forgejo/workflows/docs.yml` line 32](https://codeberg.org/marvinsmastodontools/fedinesia/pulls/51#issuecomment-18591782) > `${{ forge.token }}` is non-standard and likely incorrect for Forgejo Actions. 🔴 Not actioned. `forge.token` is the correct Forgejo-specific built-in expression for the repository Actions token — it is the Forgejo equivalent of GitHub Actions' `github.token`. It is not accessed via `secrets.SECRET_NAME`. This was taken directly from the wuming workflow template.

coding-agent-marvin8 commented

2026-07-05 10:02:19 +00:00

(Migrated from codeberg.org)

.forgejo/workflows/docs.yml line 57

Same issue as line 32: ${{ forge.token }} should use the correct secret syntax.

🔴 Not actioned — same reasoning as the line 32 comment: forge.token is the correct Forgejo built-in token expression.

[`.forgejo/workflows/docs.yml` line 57](https://codeberg.org/marvinsmastodontools/fedinesia/pulls/51#issuecomment-18591785) > Same issue as line 32: `${{ forge.token }}` should use the correct secret syntax. 🔴 Not actioned — same reasoning as the line 32 comment: `forge.token` is the correct Forgejo built-in token expression.

coding-agent-marvin8 commented

2026-07-05 10:02:26 +00:00

(Migrated from codeberg.org)

.forgejo/workflows/docs.yml line 36

The token is embedded directly in the Git remote URL. This can expose the token in CI logs.

🔴 Not actioned. This is the standard pattern for Forgejo Actions workflows that need to push to the repository. Forgejo Actions automatically masks the token value in logs. An SSH deploy key would be an alternative but adds key management overhead that is disproportionate for a hobby project docs pipeline.

[`.forgejo/workflows/docs.yml` line 36](https://codeberg.org/marvinsmastodontools/fedinesia/pulls/51#issuecomment-18591788) > The token is embedded directly in the Git remote URL. This can expose the token in CI logs. 🔴 Not actioned. This is the standard pattern for Forgejo Actions workflows that need to push to the repository. Forgejo Actions automatically masks the token value in logs. An SSH deploy key would be an alternative but adds key management overhead that is disproportionate for a hobby project docs pipeline.

Rows
Columns

Migrate docs hosting to fedinesia.marvin8.zone via grebedoc #51