I use psql and/or interact somehow with a postgres database about once every six months, so because of how my brain (fails to) store information it's a brand new and exciting experience every time. This time also involved a docker-compose network, for added spice.
docker (8 out of 8)
- Work stuff. By the way, OCCRP is hiring developers.
- Dabbled in Postgres (yes yes I know I'm a late bloomer).
- Dabbled in docker-compose.
- Dabbled in RabbitMQ.
- Climbed Trebevic with bengo.
- Finished Season 2 of Sense8. The most unrealistic thing in the whole show is how do Nomi and Neets afford that apartment in SF? Started Season 2 of the Expanse.
- Got some of my thesis corrections done.
- It got cold in Sarajevo :( I forgot how to handle this.
In reply to: https://rhiaro.co.uk/2018/12/madness
Madness also involves talking to yourself right, because I just said "oh haha that's fucking hilarious" out loud to this docker container in a restaurant* in like a regular conversational voice.
* The same restaurant in which I was cry-laughing at tumblr (RIP) screenshots earlier, but fortunately there has been a complete staff and customer turnover since then.
Madness is doing the same thing over and over and expecting different results. But this is also the only way I've figured out how to work with docker.
(I swear I must be a fucking idiot, this happens every week, please nobody hire me to do software development oh oops.)
Waiting for a docker image to build? That's time for at least 100 words.
Week in review: 18 - 24 September
Stuff on my shared hosting being broken wasn't enough so I fully broke everything on my Digital Ocean server as well. Including irc. Centralised communication only for the rest of this evening please.
Did I mention I hate computers?
HTTPS: whaaaaat
Following on from a terrible experience, I discovered that indeed Gold had taken over port 443. As soon as I kicked it off, I could launch the nginx proxy container with -p 80:80 and -p 443:443. So now the proxy knows where to find the key and cert, and is trying to load the subdomain over https, but is getting connection refused. The proxy docs say this might happen "if the container does not have a usable cert" so now I have to find out what is wrong with my cert?
Is it permissions? It's usually permissions. Nginx might reject things if they key is world readable? Tried setting to 0600 for the key and cert. No dice.
What next?
Docker makes deploying everything so super easy and fun.
Except when it doesn't.