You’ve got your backend, a marvelous piece of code sitting comfortably in a container. And there it is - a beautiful frontend. The drop-in shadow on the buttons just makes you want to lick them. Of course it’s containerized as well. And the problem arises: how can the frontend know where the backend is? The only problem with static frontends in that regard is that they are… well… static. Seams trivial, but this is a surprisingly annoying one - partly because it occurs in the JS-land yet requires a devops mindset to solve reasonably.

Disclaimer: this is an alpha version, expect updates Prologue It’s been a while. Recently I’ve started a cryptography course at the university and this correlates with people asking me about cryptography. But of course correlation is not causation… Anyway, Scott Hanselman had made an excellent take on the subject of abiding the DRY rule while passing on knowledge and in that spirit I’d like to act out the hero myth; of the one who embarked, explored and came back to talk about one’s findings.

Preface Hello, internet! Did you know that there are some problems you cannot tackle by simply heading to Stack Overflow? I was doing a Terraform setup for an analytics system. And with big data comes mighty visualization tool - Kibana. Because of networking, I’ve already had a proxy set up to forward traffic from the world to Kibana, yet some kind of security measure was required to ensure only our client has access to it.

“Chancellor on brink of second bailout for banks” ~ The Times 03/Jan/2009 Erm… There were other things here before, but they no longer apply or belong somewhere else. A begining is needed. We all know how it goes, but it must be said anyway. Well, this is it. I have spoken.