What do you take on when you host Gitea yourself?
Gitea provides the website where your team shares code and reviews pull requests. You choose where it runs, then maintain the service, its data and access. Name someone to apply updates and respond if the service stops.
Check the installation documentation for the database, data storage and settings your setup needs. A hosted service may be a better fit when nobody can look after those pieces.
What should a backup include besides Git history?
Gitea stores information in repositories, a database and other files. Its backup guide calls for stopping the instance during backup so the pieces agree. Check what your setup stores separately, including attachments and configuration.
A clone keeps code history but cannot recreate a project’s issue discussions, accounts or service settings. Before restoring, confirm the database, files and credentials all belong to a disposable copy and that email and other outgoing services are disabled or test-only. If you cannot verify the connections, use the paper exercise. Check the repository, issue, attachment and sign-in separately before calling it usable.
What will you pay for and what can move?
The self-hosted Gitea project is MIT-licensed. Budget for the server, storage, backups and maintenance. Keep the version and installation settings with your recovery record so you can reconstruct the test instance.
How would you know whether your copy is complete?
Draw a fictional project on paper. Use no instance, production backup, account or connection.
- List what should come backInclude a commit, an issue and an attachment.
- Split the checksDraw the Git history, database and file storage separately. Mark the issue and attachment unverified if the only copy is Git.