Hello everyone,
I’m currently in the process of evaluating Gitea as a self-hosted Git solution for our small remote development team (4–6 developers). We’re looking for something lightweight, easy to maintain, and with solid support for collaboration features like issues, wikis, and basic CI integration.
I’ve done some initial testing in a Docker container and so far I’m very impressed with how fast and responsive Gitea is. That said, before we commit to migrating from our current cloud-hosted Git solution, I wanted to ask the community here for some advice on best practices.
Specifically, I’m interested in:
- Recommended server specs and configuration for hosting ~10 private repositories with moderate activity (mostly Python and JS projects).
- Best practices for user management and access control in a small team setting.
- Advice on backup and restore strategies—how do you all ensure resilience in case of failure?
- Suggestions for integrating Gitea with lightweight CI/CD (e.g. Drone, Woodpecker) and how seamless the experience has been for you.
- Any gotchas or caveats you’ve run into while self-hosting—things you wish you knew early on?
Our stack is mostly Linux-based (Ubuntu Server) and we’re comfortable with Docker and Nginx. We’re also exploring ccsp training in bangalore to strengthen our cloud security posture. We’re trying to strike a balance between ease-of-use and control, so any input from folks who’ve walked this path would be greatly appreciated.
Thanks in advance, and looking forward to learning from the Gitea community!