Skip to main content

DIY trekking pole ridgeline accessory

I have setup my shelter with my trekking poles to support the ridgeline but one thing I hate is that it never feels secure (to the pole). No matter how many times I wrap the cordage or the type of knot it's always a challenge. So I did it myself.

TOOLS:

  • gorilla glue
  • trekking pole
  • mallet
  • grommet kit
  • webbing (this happens to be tubular; can make it lighter)

tools

two nine inch segments of webbing

the first band
The webbing was too strong for the punch in the grommet kit. In the end I needed to use a scissor to make the hole and a stake to hold the hole open while I inserted the grommet. The side strap ended up being about 5 inches and not the 9 that I initially cut.

installed grip down
This contraption makes it easier to move the pole around but harder to get started. (see grip up)

installed grip up
Notice that the side strap keeps the contraption from falling off the pole. The grip up configuration means that toe can be locked into the ground similar to a stake.

the finished project

Overall the project works, however, it can be made lighter. [a] shorter length [b] single ply [c] one grommet and glued loops or even just a hole melted open.

Popular posts from this blog

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…

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.

Weave vs Flannel

While Weave and Flannel have some features in common weave includes DNS for service discovery and a wrapper process for capturing that info. In order to get some parity you'd need to add a DNS service like SkyDNS and then write your own script to weave the two together.
In Weave your fleet file might have some of this:
[Service] . . . ExecStartPre=/opt/bin/weave run --net=host --name bob ncx/bob ExecStart=/usr/bin/docker attach bob
In sky + flannel it might look like:
[Service] . . . ExecStartPre=docker run -d --net=host --name bob ncx/bob ExecStartPre=etcdctl set /skydns/local/ncx/bob '{"host":"`docker inspect --format '{{ .NetworkSettings.IPAddress }}' bob`","port":8080}' ExecStart=/usr/bin/docker attach bob
I'd like it to look like this:
[Service] . . . ExecStartPre=skyrun --net=host --name bob ncx/bob ExecStart=/usr/bin/docker attach bob
That's the intent anyway. I'm not sure the exact commands will work and that's partly why we…