[Placeholder] Forgejo integration

[vcoisne]

Integration Request: Forgejo
Bounty: $500

What to back up

Forgejo instance data: repositories, issues, wikis, user data, and configuration — using Forgejo's built-in dump tooling.

Minimum requirements

• Invoke forgejo dump or equivalent to produce a backup archive
• Ingest resulting archive into a Plakar snapshot
• Restore: extract snapshot content back to a Forgejo-loadable state

Reference

• Forgejo backup docs: https://forgejo.org/docs/latest/admin/backup-and-restore/

How to claim

Comment on this issue to claim it. One active claim at a time. 2-week completion window. First merged PR wins the bounty.

[Alex-Parejo]

I’m interested in the Forgejo integration and want to align scope before claiming, per the bounty policy.

A few implementation questions:

1. Should the integration live in PlakarKorp/integrations as a new community source/connector named forgejo?
2. Is the expected backup path to execute forgejo dump locally on the host where Forgejo is installed, or should it also support remote SSH/container execution in the first version?
3. For restore, is producing/extracting the Forgejo dump archive back to a target directory sufficient for tier3, with the admin then running Forgejo’s documented restore steps, or do you expect the integration to invoke restore commands directly?
4. Should tests mock the forgejo dump command and validate archive ingestion/restore layout, or do you require an integration test against a real Forgejo container?

If that scope is acceptable, I can claim and start with a minimal dump/restore implementation plus docs and tests.

[vondutchi]

I would like to claim this Forgejo integration bounty.

Implementation plan:

• add a new forgejo integration under PlakarKorp/integrations with importer and exporter connectors
• importer runs Forgejo's native dump command, streaming forgejo dump --file - --type tar.gz into a Plakar snapshot
• support the common Forgejo CLI paths/options: binary path, work path, custom path, config path, temp dir, database syntax, and dump type
• exporter restores by extracting the archived dump contents to a target directory so the result is in a Forgejo-loadable state for the documented restore flow
• add schemas, README usage notes, and unit tests around command construction and archive extraction

ETA: first reviewable PR within the 2-week window, aiming much sooner.

[Alex-Parejo]

I opened a scope-alignment draft in PlakarKorp/integrations: https://github.com/PlakarKorp/integrations/pull/26\n\nI am still not treating this as a final bounty claim until you confirm scope. The draft implements the local tier3 assumption: run orgejo dump --type zip, snapshot the dump archive, and export it back to an output directory for an administrator-led restore.

[IvanchitorJR]

I would like to claim this bounty.

Planned scope: add a Forgejo integration in PlakarKorp/integrations with a forgejo:// importer/exporter. The importer will invoke Forgejo's built-in forgejo dump command to create a backup archive, then ingest that archive into a Plakar snapshot. The exporter will materialize the snapshot content back into a Forgejo-loadable dump archive/directory for restore workflows.

I will keep the implementation focused on the minimum requirements in this issue and reference the Forgejo backup docs in the README.