Skip to main content

Home made hydration system

For not particular reason I'm not a fan of "the hydration pack". First of all they are expensive relative to the smartwater bottle. Second they are not as ubiquitous as the smartwater bottle And third but not last the bottle works great with most water filters. And let's not forget the first purchase includes water for free.

And so I implemented a DIY smartwater hydration project. I particularly like this project because my Yukon Outfitters El Capitan pack has deep web pockets, 

smaller bottle has a spout
Step 1: buy a smartwater 1L and .8L bottles

Notice that not all the water bottles have the spout. The spout is required for this project but not in general. This project is only part of my water system which includes my sawyer filter. An original spout or syringe is required to flush the filter

the spout removed from the bottle

Step 2: remove the spout from the bottle.

Step 3: the original opening is not actually wide enough for the tube so hollow it out just a little.

Step 4: remove the lid from the spout

Step 5: measure the tube against the 1L bottle to get an approximate position for the spout

Step 6: run the tube through the modified spout and superglue it into position

Step 7: (not pictured) install the mouth piece to the other end of the tube

Installed on haversack - this pack has shallow web pockets and no place to secure the tube on the shoulder harness. Notice I used some green/black shock cord. (bottom right)

Installed on Yukon El Capitan there is a built-in green restraint on the shoulder harness.

The best part about this project is that I do not have to clean the hydration bag. Just replace the bottle as you would normally. This could prevent some nasty side effects although you still have to clean or replace the tube and mouth but this can be done with a sterile wipe or boiling water (this will fit in a stanley pot).

Popular posts from this blog

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…

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…