Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing Fossil vs Gitea, the Slant community recommends Gitea for most people. In the question“What are the best bug/issue tracking tools for small development teams?” Gitea is ranked 5th while Fossil is ranked 10th. The most important reason people chose Gitea is:
Easy to install and setup. Can run on a VPS with 1 core CPU and 256MB RAM.
Specs
Question Ranking
Pros
Pro DSCM + issue tracker + wiki
If you need a (distrubuted) SCM, Fossil comes with a built-in SCM, a wiki and issue tracker.
Pro Self-contained file
The data is stored in one single file. No file structure distributed over a bunch of folders.
Pro Multi platform
The executable is provided for multiple platforms, e.g. Linux, macOS, Windows.
Pro Easy to install
The Fossil application contains one single file. No need to install dependencies.
Pro Light-weight
Easy to install and setup. Can run on a VPS with 1 core CPU and 256MB RAM.
Pro Open source and maintained by community
Unlike Gogs, which is maintained primarily by its creator.
Pro Intuitive interface
Easy to navigate around and feels very natural in general.
Pro Non-memory consuming
Just like Gogs, but with new features and fixed bugs. Unlike GitLab which is enormous.
Pro Wiki and issues
Like GitHub, a wiki and issues (bugtracking) can be added to a repository.
Pro Fast pace of development
New features, constantly updated.
Pro Like Gogs but with faster bug fixes
If you love Gogs but were frustrated with the long wait for bugs to be fixed, this is for you.
Pro Most common platforms
Versions available for Linux, Mac and Windows. This is possible because Gitea is developed in the Go language which makes it compact and fast too. Only one executable is needed.
Pro Easy install with MariaDB back-end
No problems getting to work with MariaDB.
Pro Simple to install/written in GO
Pro Package Registry
Supports NuGet, npm, Cargo, Composer, Maven, RubyGems etc.
To work with the NuGet package registry, you can use command-line interface tools as well as NuGet features in various IDEs like Visual Studio.
Pro Runs perfect on a Raspberry Pi 3
Thanks to its light-weight and simple integration.
Pro Customizable Templates
All templates can be overridden.
Pro Focus only on key features
And if you want extra features, you can use web hooks.
Cons
Con Ticket comments can't be edited
While a ticket can have multiple comments added to it, and (separately) also attachments — if the users have the right permissions — it is impossible to edit a comment after submitting it. This is probably why a comment must be previewed before it can be submitted.
