Indy Cloud Conf 2019
I gave two talks at this year’s Indy Cloud Conf. It was the first time that I have ever spoken professionally in front of a crowd. I had a lot of nerves leading up to the event, but I feel like I put my best foot out there. It was a fulfilling experience, one that I’ll certainly be looking to do again. When to rm -rf Kubernetes Kubernetes is quickly becoming the de-facto choice for container orchestration.
How hard could it be to make a multi host Postgres proxy?
Imagine a scenario where you want to route postgres connections through a single proxy to multiple databases. ---> Proxy ---> Database 1 ---> | ---> Database 2 How would the proxy work? We’d want to leave the actual database connection secured so the data itself would be encrypted. That prevents us from proxying based off some data in the query itself. That leaves us with a couple of options
Home Assistant, and Kubernetes, and Z-Wave, Oh My!
Home Assistant + Z-Wave For the last 3 years or so, I’ve been running Home Assistant for my home automation needs. I’ve gone through a couple iterations with it being hosted on bare metal on a raspberry pi, in a python virtual environment, and within a docker container. I started off mainly with just smart lights so wi-fi bulbs worked pretty well. After time, concerns with security and general scale led me to start using Z-Wave and Zigbee devices.
When Errors are Promises
Under what circumstances will the following code end up logging the rejected promise message to the console? foo() .catch((err) => { console.log(`Promise Rejected. reason = '${err}'`); }); When foo returns a rejected promise like so const foo = () => { return Promise.reject('Rejected Promise'); }; The console will look like Promise Rejected. reason = 'Rejected Promise' Now the naming of catch makes it seem like it should also handle errors. If foo looks like