&gt; Fossil&#x27;s wiki and ticketing system are awful<p>Care to be more specific?<p>I&#x27;ll grant that Fossil&#x27;s wiki is not a competitor to MediaWiki, but that doesn&#x27;t make it &quot;awful.&quot;  It just makes it less featureful.  So, what feature do you need in a wiki that Fossil&#x27;s wiki does not provide?<p>As for the ticketing system, again, it isn&#x27;t going to replace the big boys out of the box, but it also doesn&#x27;t have to match them feature-for-feature to be useful. Also, the Fossil ticketing system&#x27;s behavior is not fixed: it can be modified to some extent to behave more like you need. Did you even try modifying its behavior, or are you just complaining about its out-of-the-box defaults? Be specific!<p>&gt; unexpected behavior for basic commands like &quot;fossil rm&quot;.<p>If you mean that you want fossil rm to also delete the checkout copy of the file in addition to removing it from the tip of the current branch, and you want fossil mv to rename the checkout copy in addition to renaming it in the repository, then you can get that by building Fossil with the --with-legacy-mv-rm flag, then setting the mv-rm-files repository option. You can enable it for all local Fossil repositories with &quot;fossil set mv-rm-files 1&quot;.<p>Alternately, you can give the --hard flag to fossil mv and fossil rm.  That works even with a stock binary build of Fossil.<p>&gt; I&#x27;m just not super-fond of relying on Bitbucket<p>For some of us, relying on a cloud service just isn&#x27;t an option. We&#x27;re willing to give up many features in order to keep control of our private repositories.<p>&gt; a package I could toss on my own VPS? I&#x27;d toss some money at that.<p>Fossil runs great on a VPS, even a very small one, due to its small footprint. I wrote a HOWTO for setting it up behind an nginx TLS proxy using Let&#x27;s Encrypt here:<p><a href="https:&#x2F;&#x2F;www.mail-archive.com&#x2F;fossil-users@lists.fossil-scm.org&#x2F;msg22907.html" rel="nofollow">https:&#x2F;&#x2F;www.mail-archive.com&#x2F;fossil-users@lists.fossil-scm.o...</a>