Well I have my #fossil server setup with SSL and all that good stuff. Most of the hassle was dealing with #Apache cgi support (which I haven't touched since before the year 2000) and your basic unix permissions, etc.
Working on a blog post as well...
@cstanhope For me those features are key to getting away from the proprietary "value-add" of Github, Gitlab, etc.
But yeah if I didn't need that Git+ssh remotes would be way easier.
@jjg You're reminding me why I got into fossil the first time. I only moved away from it as I wanted to practice using git. (I wasn't using git at my work at the time.) It's very strange to me that the ideas of fossil haven't been applied to git and hg. But perhaps the "value-add" services were "good enough".
I think for most of the world Github *is* Git (unfortunately). At least most of the developers I encounter IRL don't understand that there is a way to use Git outside of the Github website.
I wish #fossil had a "federated" mode that didn't use centralized servers. I think it might be easier with fossil because it already provides a "local mode" web UI, so you just need a background protocol to synchronize the repositories between collaborating hosts... 🤔
@jjg That's a good point about the confusion between git and Github. There's also a subset of developers that want everything to be on Github so they can fluff up their profile with all their activity. Anyway...
It really would be interesting to extend fossil in ways that allow synchronizing repositories without needing a centralized web presence.
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!