I’ve been a bit envious of the activity graph that Github creates for the checkins happening across all repositories by a developer.
Since I’ve always been using fossil across projects, I thought I could do the same with fossil as well.
Fossil repositories being SQLite databases themselves made things a bit easier.
Continue readingI got this fossil error during the latest server setup on Ubuntu. Earlier, it was just the question of adding fossil to the path.
But for some weird reason, I got this error this time –
home directory "" must be writeable Aborted (core dumped)
After trying to search for the error, I finally got a clue at this fossil check-in, which shows the check for write access to the home directory to create a .fossil file.
Checking all accesses, everything seemed absolutely correct, so the only thing left to do was to create the file manually –
touch ~/.fossil
This solved the problem correctly.
To get git to exclude files and directories, we need to add a .gitignore file in the root folder of the project.
Some of the things I learned from setting up my .gitignore
Once fossil is set up, I wanted it to start automatically on system reboot, so that I needn’t worry about it in the future.
After trying many different ways of doing this and failing, I ended up with a configuration which included a shell script and supervisor to start it.
Continue readingSetting up Nginx with fossil is also not too much of a problem.
Essentially, nginx has to be redirected to the /repos path to be able to work with fossil server command correctly.
Continue readingI’ve always been a fan of Fossil which has been my go-to version management system since ages.
I wanted to set up fossil for all the code that I write. Fossil being a single binary file which I can put anywhere (and add that to the path) has always been a breeze to use.
Continue readingCopyright © 2025 the möbius trip
Theme by Anders Noren — Up ↑