Skip to main content

to Golang HOME or some place else?

I'm trying to cleanup all the junk on my computer; and there is a lot of junk. The hard part is the quantity of files not the size. As part of the Golang idiomatic way there are at least 3 places where "we" store packages.

(a) GOROOT - which is typically reserved for the compiler. Go's get function may let you do it if you override GOPATH for that request but it's probably not the best thing to go.

(b) setting GOPATH=$HOME - this is the usual way to do things, however, this means you are going to end up with a src, pkg, and bin folder in your $HOME. This is not a totally bad thing but just messy. Partly because you have 3 new folders in your HOME but you could inadvertently override another executable with the same name in your bin folder... as this bin folder is shared between your normal apps and your apps from source.

This is further messy because the order of the paths in the PATH environment variable is the order that they are evaluated when looking for an executable... so you could end up executing the wrong one.

(c) setting GOPATH=$HOME/gorepo - this means that the 3 folders I mentioned would be located in the gorepo folder. This seems better because we have segregated the packages and binaries from the rest of my everyday stuff. Development is partitioned away from the every day.

Now the only concern is that while I'm importing code from every corner of the github and bitbucket universe I'm polluting my gorepo folder with code that I did not write but with vendor code that others did. Frankly there are times when I just like to clear the decks and delete the vendor code. Now what do to?

  • create a gorepo and put my code in there
  • inside gorepo create a vendor folder shared by all
  • implement proper project vendoring when applicable
  • make sure my projects use the proper folder structure that maps to the VCS path
  • fork projects to your repo when practical
  • "configuration as code" - use a Makefile with simple commands
that should do it... even though it still means having more that one path in your GOPATH.

QUESTION: Where do you put repos that you want to inspect, fiddle and possibly fork later on? Since the full path is part of the namespace if your fiddling includes importing these projects you're going to be forced into changing the imports. So maybe "import early"?

UPDATE: Rats! Maybe GOPATH is just better being $HOME and sucking up the deps in the same folder?

UPDATE: Andrew Gerand wrote a good article on the subject.

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…