I have a few things on the go but there are a couple that could do with a wider audience for testing.
The first one is erbmash; a standalone binary that takes an erb template and optionally a json / yaml file and parses / renders it. The primary motivation was for initializing container configuration but recently I found it helpful in reducing the boilerplate in creating an HTML slide deck with shower.js.
It could really do with some wider testing and feedback so if you like the sound of it, please have a look.
The second one is a tool for folks stuck behind corporate proxies. They get in the way no end and are particularly problematic for laptops that get taken home / off site. Especially if you run VMs or docker on it (or even docker in VMs!). When you provision a VM inside the corporate network you need to set the proxies. Then, when you take the machine home the VM no longer has connectivity because it's trying to use the proxy.
Similarly, when you set HTTP(S)_PROXY env vars, cli tools always blindly use these. Rarely are the network rules so simple that ALL connections should go through the proxy so requests to some local machines fail.
I wrote a tool called pacyak that proxies proxies. I run it locally on my laptop and set all of my proxy settings to 127.0.0.1:8080. For VMs I use vagrant-proxyconf with VAGRANT_HTTP(S)_PROXY set to 10.0.2.2:8080. This allows VMs and docker to work inside or outside the corporate network without having to change their proxy settings.
When pacyak detects you're on the corporate network, it will use the PAC file provided by your company (most have one) to decide which proxy to use or not. This resolves the issue with CLI tools inappropriately using the proxy.
Again, it could really do with some wider testing and feedback so if this is a problem you have, please give it a shot and let me know how it works (or doesn't) for you.
I have a few things on the go but there are a couple that could do with a wider audience for testing.
The first one is erbmash; a standalone binary that takes an erb template and optionally a json / yaml file and parses / renders it. The primary motivation was for initializing container configuration but recently I found it helpful in reducing the boilerplate in creating an HTML slide deck with shower.js.
It could really do with some wider testing and feedback so if you like the sound of it, please have a look.
github.com/mikesimons/erbmash
The second one is a tool for folks stuck behind corporate proxies. They get in the way no end and are particularly problematic for laptops that get taken home / off site. Especially if you run VMs or docker on it (or even docker in VMs!). When you provision a VM inside the corporate network you need to set the proxies. Then, when you take the machine home the VM no longer has connectivity because it's trying to use the proxy.
Similarly, when you set HTTP(S)_PROXY env vars, cli tools always blindly use these. Rarely are the network rules so simple that ALL connections should go through the proxy so requests to some local machines fail.
I wrote a tool called pacyak that proxies proxies. I run it locally on my laptop and set all of my proxy settings to 127.0.0.1:8080. For VMs I use vagrant-proxyconf with VAGRANT_HTTP(S)_PROXY set to 10.0.2.2:8080. This allows VMs and docker to work inside or outside the corporate network without having to change their proxy settings.
When pacyak detects you're on the corporate network, it will use the PAC file provided by your company (most have one) to decide which proxy to use or not. This resolves the issue with CLI tools inappropriately using the proxy.
Again, it could really do with some wider testing and feedback so if this is a problem you have, please give it a shot and let me know how it works (or doesn't) for you.
github.com/mikesimons/pacyak