Fossil is the best. Sqlite uses it

▲ bigfishrunning a day ago | parent | next [-]

Fossil was written for Sqlite in the same way that git was written for Linux. It's really a shame that more projects don't use it. I think that a github competitor (with social features, PRs, CI, etc) with a fossil backend would be very popular.

	▲	somat 16 hours ago \| parent [-]
		In fossil's case, every instance includes those features, this makes the social platform "the web itself" Having said that, there are central hosting projects, but where that has some value with git, git proper is distributed and does not need it but all the auxiliary stuff does. with fossil it provides almost no value. All the auxiliary stuff is built in so all it provides is a place to host. Which is fair but hosting is not hard with fossil. https://chiselapp.com/ With everything included in fossil I abuse it as a personal social platform(think discord) super easy to host and it gets me chat, forums, wiki, and file storage. None of them great, but it is so easy I don't really care. voice and video do require an additional service, so there is that. Now I just need to find some friends...

▲ rpdillon 20 hours ago | parent | prev [-]

Yep, I use Fossil for all my side projects. Super easy to host, tiny, includes everything I need for a project, all in one file. Great piece of software.

▲ yellowapple 17 hours ago | parent [-]

I've been gradually migrating my Git repos to Fossil as I've been touching them. Been quite happy with it.

There are only a couple things that I miss:

- Grouping repos together into a combined project. I'd love to be able to have a single Fossil server/instance with a single set of users, wiki pages, tickets, etc. but multiple independent codebases. Closest I've gotten to that is to simply have multiple independent branches instead of a single trunk (example: https://fsl.yellowapple.us/avorion/home), and it's worked surprisingly well, but it's clear Fossil wasn't designed with this workflow in mind, so there are some rough edges with it (albeit minor and easy to work around).

- Compatibility with things that assume you're using Git. Being able to export to Git helps a lot here, but it's still extra steps. Ideal solution here would be for the Fossil server to be able to double as a Git forge and present repos accordingly, such that I can point things like CI/CD pipelines or Terragrunt module calls or whatever directly to the Fossil repo itself over the Git interface those things expect instead of having to setup a Git forge manually and somehow synchronize everything w.r.t. access controls.

- An equivalent to Git's submodules. This would IMO help address the “grouping repos together into a combined project” case as well.

	▲	somat 16 hours ago \| parent [-]
		There are login-group options which lets you have a single sign on with a group of repos, To unify the other bits it looks like it would be possible to change the main menu links to the central repo(in the web settings). Never wanted to do what you want but it sounds possible set up the fossil server on a directory of repos probably with --repolist to get a list `fossil server --repolist /var/fossil/` get all repos in the same login-group change the menus in each repo to point to the core repo. Based on some quick tests I suspect a full http:// url is required. `- Forum /forum {@2 3 4 5 6} + Forum https://mydomain.org/core/forum {@2 3 4 5 6}`