What is the difference between Forgejo and Codeberg?
Forgejo is the software. Codeberg is a hosted community service with its own eligibility rules. If you run your own Forgejo instance, choose who can create repositories, how teams sign in and who maintains the service.
Check the installation and upgrade paths before sharing a repository with your team. Keep responsibilities clear even when someone else supplies the server.
What would you need if an upgrade fails?
Keep a consistent copy of repositories, database and any separately stored files. Forgejo’s upgrade guide calls for a full backup before moving to a new stable release. Its backup guide strongly recommends stopping Forgejo during backup so the stored pieces stay consistent.
Record the version, settings and storage locations for the backup. Before restoring anything for a rehearsal, verify that the actual database and file destinations belong to the isolated test instance. If you cannot confirm the destinations, use the paper exercise. Before starting the restored instance, check that email, webhooks, automation and other outgoing connections are disabled or test-only.
What does Forgejo cost to run?
Forgejo releases from version 9 use GPL version 3 or later. Budget separately for hosting, storage, backup and the operator’s time. Keep a Git copy for the code and a service backup for issue records, account settings and other project data.
What should you verify on a test copy first?
Sketch a fictional issue and one associated commit. Use no server, credentials, storage or actual upgrade.
- Draw the test destinationMake a new box for the service, database and files. Cross out live notification, automation and storage connections.
- Name the expected resultsWrite which commit and issue should appear. Keep both results unverified until the isolated copy is inspected.