Skip to main content

business idea : seasonal tiny living

I was just watching a video about a couple who decided to give up living in the city to live in a tiny trailer.


I live in a 4 bedroom house, work from home, kids are in elementary school, and a wife who is a teacher. Our mortgage and escrow is about $2300 a month and while I purchased the house before I was married with kids I see the advantages of tiny living.

First of all, even if you're tiny living on-grid the smaller the place the less stuff you can store and so space is an important trade-off. Depending where you locate your tiny homestead you might have fewer expenses overall. Smaller place less A/C. Let's say you want to upgrade to granite counter tops well surface are equals cost.

Ten years ago I rented a log cabin in North Carolina for a week. I think I paid about $1100 for the week. The cabin slept 17 people but we were only 6 adults. It was a great week and we had a lot of fun. There wasn't much storage and we did not have much stuff. There were a couple of closets that were locked and that was probably where the owners stored their stuff.

Wouldn't is be great to be able to rent a tiny space for a season? Wouldn't it be great to be a tiny house landlord? I think about where we live and our friends and peers... it couldn't happen here as there is no available land here; which would mean leaving our community.

That could go either way.

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…