{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiacir5hglfjmumppfpawyaiisd5lg6dxjzf3vqnv2z3evufp5cjua",
    "uri": "at://did:plc:hwpfviglvxef74s5w4fhywt7/app.bsky.feed.post/3mdteshxnfgx3"
  },
  "contributors": [
    {
      "did": "did:plc:dqehxkfb3kv6bx7tfkvyzdt4",
      "role": "author"
    }
  ],
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreid7fbew5lflspu7csbwuy7drkzqggegvqhrb4pr2fofymvsnaexma"
    },
    "mimeType": "image/png",
    "size": 43048
  },
  "description": "Six years ago, I described my system for configuring a reverse proxy for docker containers. It involved six containers including a key-value store and a webserver. Nothing in that system has persisted to this day. Don’t get me wrong – it worked – but there were a lot of rough edges and areas for improvement. Microservices and their limitations My goal was to follow the UNIX philo...",
  "path": "/docker-proxying-redux/",
  "publishedAt": "2022-12-06T00:00:00Z",
  "site": "at://did:plc:hwpfviglvxef74s5w4fhywt7/site.standard.publication/3mnmr7tmggs2e",
  "title": "Docker reverse proxying, redux"
}