Skip to main content

fishshell, boot2docker and my config

I like fishshell for a number of reasons with my favorite being the CLI. While it does not support ^R, out of the box, in order to search the command history it feels a lot more natural. Just start retyping the desired command and it will find and highlight the previous versions which you can scroll and select. Of course it has the weakness that if the first few letters of the command are not the same as the next command then there is some CLI navigation gymnastics... but at least the normal operation is the normal operation.

I suppose I have gotten used to the fact that the .bashrc and .profile files are in the $HOME folder because when fish decided to put it's config file here: $HOME/.config/fish/config.fish I could never remember the exact folder and in some cases I could not be bothered to search the docs. This is part of my green folder initiative.

My fish/config.fish looks like this:
set -x fish_user_paths $HOME/binset -x GOPATH $HOMEgo env|grep GOROOT | sed -e "s/\(.*\)=\(.*\)/set -x \1 \2/" |source
The first line adds my bin folder to the PATH environment variable without having to do the work myself. If memory serves the function will check for dupes. This may or may not be a bad thing if order is important... and it should never be.

The second line is obvious. It's just creating the default GOPATH. This is just temporary because there is an idiomatic way to manage the GO environment. I think the GO authors intended for users to set the variable manually or as part of a make/build so that the environment was semi sandboxed and idempotent.

Then the last line. I'm attempting to extract the GOROOT from the current GO cmd and then set the environment in the fish-way. What's interesting is that GO is supposed to figure out it's own GOROOT but it's not very good at it in fish.  I suppose I could have hard coded it, however, I have been known to swap between the homebrew installation of GO and the source or binary directly from GO. I like homebrew because it's fast and easy to install, uninstall, update and upgrade. Not forget that they offer some feature flags for cross platform and others. I hope they stay current.

Finally, absent from the config file is the boot2docker and docker commands. I'm on the fence with this because setting the docker/boot2docker environment is easy but it means that boot2docker has to be running in the VM and I'd rather do that selectively. I tend to move around between local and remote development. So making it optional is better.

Note that the output from the `boot2docker shellinit` command is compatible with fish and while you might use:
$(boot2docker shellinit)
in bash; in fish you'll use:
boot2docker shellinit | source
The changes to the environment are exactly the same.

Comments

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: http://www.eeti.com.tw/drivers_Linux.html (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 setup.sh answer all of the questio…

Prometheus vs Bosun

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

TL;DR;

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…