CODEX

Alright, curious people of the internet. In my previous article we’ve explored how one might creatively rebuild internals of an ordinary laptop pad. Now it’s about the right time to get to The Controls of The Creature. But before we jump in, let’s recap what I willingly was dealing with. And those things are:

• two DHT22 sensors I wanted to read measurements from
• the cluster of PWM fans I wanted to have a control over
• the lights wired-up via RPi’s PWM I wanted to have a control over as well

Eye on the ball — the only what matters is goal.

The ultimate goal was to make the pad to be…

Introduction

Somewhere last year I’ve got a cheap Amazon-purchased pad with five fans inside. And so no expectations then. Pretty soon both USB inputs started to act up and eventually the thing has stopped both cooling and being cool. Perhaps it has never been the latter. Anyhow, I decided to fix both.

The same title has Google docs article. Apparently it addresses the go1.11 to 1.12+ migration changes. And like many other docs by Google I’ve found this one to be a bit cryptic.

In my previous articles I’ve described how to setup Identity-Aware Proxy for your Go App Engine app and then coped with some unit-testing in two parts (one and two). It was all go1.11. Now lets do the same with go1.12+.

But first, lets recap the changes I’ve thought of as vital:

• google.golang.org/appengine goes away. That means everything you’ve used straight from the package (context, logs, services’ APIs etc.)…

In my previous article I’ve addressed some of the local unit-testing problems for your Go1.11 AppEngine app. But that all ain’t quite far from the standard docs by Google. And not entertaining at all. So let’s move on from hello-world towards a real world.

In the real world you would have to deal with data. And at some point you would have to store the data you’re dealing with to somewhere and to retrieve it later from that somewhere. …

Once upon a time I’ve been given with a test task. The task was to scrape a bunch of pages using a certain python-based framework. To be modest, I did alright, I was assessed nicely with one huge remark: no unit-tests. That has been eventually a sentence — they denied my application. Who I’ve been after that? A pro? Not quite. An imposter? Perhaps closer. Regardless of the answer, lesson’s learnt. So let’s talk some unit-tests for your Go 1.11 application in Google’s AppEngine.

In my previous article I’ve come up with a hello-world application, which does next to nothing…

There’s a lot have been said about how to secure it, but not that much said about what is it that you should do next? Use it, I guess? I’ve been struggling getting to know how the things may and should work and would like to share my somewhat painful experience.

Deploying your application

Assuming you have an app structured the following way:

.
├── go.mod
├── go.sum
├── server
│   ├── app.yaml
│   └── main.go
└── service.go

The app has nothing interesting so far, service just holds WarmupRequests handler, main holds routes and app.yaml is at its basic form. …