Skip to main content

Fossil SCM - work flow

I have really started to take a liking to Fossil. I have been using it for a current project and while I could have easily use BitBucket or GitHub this is not the sort of project I want to risk sharing until it's time. And while I could have self hosted BB and GH it's a lot more trouble than it's worth.

Fossil is produced by the same developers that are responsible for SQLite. In fact SQLite is embedded. One of the better references is the Concepts page.

What follows is a loose list of ordered commands for setting up your distributed environment for multiple users.

Install fossil on the server and the local machine(s)
In most cases it is a matter of copying the executable to a folder in the user's path. In my case I have a bin directory off of my HOME.

Initialize the repo on the remote server
(login to the remote server)
mkdir ${HOME}/fossil-repo
${HOME}/bin/fossil init ${HOME}/fossil-repo/mydemo.fossil

Clone the remote repo to the local repo
mkdir ${HOME}/fossil-repo
~/bin/fossil clone ssh://user@server//path_to_repo?fossil=path_to_fossil path_to_local_repo

Open the repo locally
mkdir ${HOME}/demo
cd ${HOME}/demo
${HOME}/bin/fossil open ${HOME}/fossil-repo/mydemo.fossil

Create a small file; add it to the repo and commit... just so there is something in the project
touch README
${HOME}/bin/fossil add .

${HOME}/bin/fossil commit -m "initial import"

Perform an update before comitting new updates in order to import changes made by others
${HOME}/bin/fossil update

**One thing I noticed was that when I installed fossil on my OSX machine I was getting a strange error "killed by signal 2". Since the error was being written to STDOUT by SSH I discovered that this command would prevent it from being displayed. It's possible that the event is being generated on all ssh versions - only OSX is displaying it. So to suppress the message:

~/bin/fossil setting ssh-command 'ssh -q'


Popular posts from this blog

Entry level cost for CoreOS+Tectonic

CoreOS and Tectonic start their pricing at 10 servers. Managed CoreOS starts at $1000 per month for those first 10 servers and Tectonic is $5000 for the same 10 servers. Annualized that is $85K or at least one employee depending on your market. As a single employee company I'd rather hire the employee. Specially since I only have 3 servers.

The pricing is biased toward the largest servers with the largest capacities; my dual core 32GB i5 IntelNuc can never be mistaken for a 96-CPU dual or quad core DELL

If CoreOS does not figure out a different barrier of entry they are going to follow the Borland path to obscurity.

UPDATE 2017-10-30: With gratitude the CoreOS team has provided updated information on their pricing, however, I stand by my conclusion that the effective cost is lower when you deploy monster machines. The cost per node of my 1 CPU Intel NUC is the same as a 96 CPU server when you get beyond 10 nodes. I'll also reiterate that while my pricing notes are not currently…

eGalax touch on default Ubuntu 14.04.2 LTS

I have not had success with the touch drivers as yet.  The touch works and evtest also seems to report events, however, I have noticed that the button click is not working and no matter what I do xinput refuses to configure the buttons correctly.  When I downgraded to ubuntu 10.04 LTS everything sort of worked... there must have been something in the kermel as 10.04 was in the 2.6 kernel and 4.04 is in the 3.x branch.

One thing ... all of the documentation pointed to the wrong website or one in Taiwanese. I was finally able to locate the drivers again: (it would have been nice if they provided the install instructions in text rather than PDF)
Please open the document "EETI_eGTouch_Programming_Guide" under the Guide directory, and follow the Guidline to install driver.
download the appropriate versionunzip the fileread the programming manual And from that I'm distilling to the following: execute the answer all of the questio…

Prometheus vs Bosun

In conclusion... while Bosun(B) is still not the ideal monitoring system neither is Prometheus(P).


I am running Bosun in a Docker container hosted on CoreOS. Fleet service/unit files keep it running. However in once case I have experienced at least one severe crash as a result of a disk full condition. That it is implemented as part golang, java and python is an annoyance. The MIT license is about the only good thing.

I am trying to integrate Prometheus into my pipeline but losing steam fast. The Prometheus design seems to desire that you integrate your own cache inside your application and then allow the server to scrape the data, however, if the interval between scrapes is shorter than the longest transient session of your application then you need a gateway. A place to shuttle your data that will be a little more persistent.

(1) storing the data in my application might get me started more quickly
(2) getting the server to pull the data might be more secure
(3) using a push g…