1. Why Deploy Independently with an Image Better SEO With GitHub Pages, deploying a static site is very convenient. Configure it once, and every commit deploys and updates automatically. Add jsDelivr and Cloudflare acceleration on top, and among free options it is already production-ready. Unfortunately, Baidu’s search engine indexes GitHub Pages sites very slowly, or not at all.

1. Github Container Registry On September 1, GitHub announced that Github Container Registry had entered public beta, offering a free, unlimited-capacity Docker image registry service during the testing period. No more worrying about docker.io wiping images out of the blue. How nice, how sweet! GitHub is using hosted code repositories as its entry point and gradually covering the entire R&D toolchain to build a one-stop DevOps platform.

1. Enabling Docker’s experimental Feature First, enable Docker’s experimental feature, so the commands below are available. Edit vim ~/.docker/config.json and add the following: 1 2 3 4 { "experimental": "enabled", "debug": true } Note that this is not the /etc/docker/daemon.json file, and Docker does not need to be restarted. 2. Docker Images Starting with Docker 1.

Usually, running a command of the form export http_proxy/https_proxy on the host is enough to set a Proxy. However, settings on the host do not take effect inside containers. Below are several configuration approaches. 1. Configure Docker’s proxy - Node level Configure this on the node that needs the Proxy.

1. Multi-Stage Builds Compiling a project requires a set of specific tools, but those tools are not needed at runtime. To reduce the image size, you can build in stages. Build in the first stage, then carry the compiled output into the next stage to produce a smaller image. 1 2 3 4 5 6 7 8 9 10 11 FROM golang:1.