Work, work, work. Eventually I managed to launch the server, but it shuts down because it can't find vault.
The problem was, Oracle has rewritten System.env, and it's impossible to update it (it depends on Java version - it would be stupid to go there). As a result, I had to write a launch script.
Got the vault url from the docs - but oops, not found, we are under vpn.
Asked on slack. Peter writes: "now you have to use" this url. The url is just one word. What kind of url is it? Well... read the docs for the project called `environment`. Wait, that's exactly what I'm reading. Oh, no, that's the docs from two days ago, it has all been changed.
And besides, I have to install gcloud, I have to install vault. Google even installs Python in the process. (I know, there's an infinite number of Python versions.)
But I have to admit, from an intellectual aspect, Google's software is way more civilized than that from Amazon.
Anyway, now I see vault. But it returns HTTP 400. Meaning, I have to send credentials. What credentials? My own, from github? There's nothing in the docs about this.
Then we had a meeting (it was half past four) Jeremey says: "since Vlad can't run it locally, let's deploy it somewhere on staging, like everyone does". Ok, do I mind? Not my monkeys. I'd say I'm ready, just tell me, which credentials.
Now Peter says: Oh, credentials don't work for me via a script (big deal, I could do it via curl), it only works via a browser. Except that Esteban can't do it via a browser, since he's in Bogota. Esteban can only do it via cli. Well, ok, agreed, let's talk tomorrow at 3pm. We planned it initially for 1:30, but Mary called me, during the meeting, and scheduled an interview for 1:30. Ok, no problem. We will see.