Go Dev Guiding Principles
An opinionated list of practices when developing in Go.
Names should be self revealing.
Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.
NOTE: This is a question I found on StackOverflow which I’ve archived here, because the answer is so effing phenomenal.
If you are not into long explanations, see [Paolo Bergantino’s answer].
docker-login repo is setup with minimal (read-only) access which allows all users to login. This creates
the necessary credentials store required for all subsequent docker operations. The team docker repositories will be setup
with RBAC to only allow access to members of that respective team to perform docker push/pull operations.
The proxy will inspect the context path for the docker pull/push operations and proceed only if authorization is successful.
|log 127.0.0.1 local2
|8.2.3. HTTP log format
|The HTTP format is the most complete and the best suited for HTTP proxies. It
|is enabled by when "option httplog" is specified in the frontend. It provides
|the same level of information as the TCP format with additional features which
|are specific to the HTTP protocol. Just like the TCP format, the log is usually
|emitted at the end of the session, unless "option logasap" is specified, which
|generally only makes sense for download sites. A session which matches the
|"monitor" rules will never logged. It is also possible not to log sessions for