GoLint
Moby
GoLint | Moby | |
---|---|---|
6 | 212 | |
3,883 | 67,768 | |
- | 0.3% | |
0.6 | 10.0 | |
almost 3 years ago | 1 day ago | |
Go | Go | |
BSD 3-clause "New" or "Revised" License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
GoLint
-
9 Golang Name Conventions Gophers should follow!
Actually in the early days of Go, devs were stuck to camalCase/PascalCase on variable naming. But VScode Go plugin managed by Microsoft at that time , and they suggested ID over id/ID, XML over xml/ Xml. Because VScode is free, it attached many users and using uppercase for abbreviations/ initialisms became a standard. Andhttps://github.com/golang/lint/issues/124 finalized it. But , still I think it is a wrong decision.
-
VS Code Extension for autocomplete function parameters and best linter?
As for linting, go vet and [staticcheck](staticcheck.io) are the recommended tools, according to the now deprecated golint repository.
-
I wrote a markdown to html converter
golint is deprecated, and it’s no longer required to comment every exported variable/function/struct, etc.
-
go config on mac
not found error (go tools not found issue explained below), can also check here
- A basic polynomial library
-
What are the REST API reference projects that can be used as a guide in 2021?
about Initialisms; Personally I still prefer simple initial conventions (lowerCamelCase, UpperCamelCase, UPPERCASE) Go followed before VSCODE/Microsoft suggested ID or Id (ex. https://github.com/golang/lint/issues/124). Following one pattern everywhere is the best. In Go, a name is exported if it begins with a capital letter. ex URL; if any unexported var/const start with "URL", what do you do?
Moby
-
Release Radar • March 2024 Edition
Having been featured in our February 2023, and January 2024 Release Radars, Moby is the original Linux Container runtime. This new version adds a bunch of changes to the Docker CLI and Moby itself with additional features. There's bug fixes and enhancements, with the main thing for users to be on the look out for containers that were created using Docker Engine 25.0.0. These containers might have duplicate MAC addresses, and thus must be recreated. The same goes for those containers created with Moby 25.0+ and with user defined MAC addresses. Read up on all these changes in the release notes.
-
Choosing a Name for Your Computer
Formlabs does this as well for their 3d printers, my earliest encounter of this was when Docker started getting popular: https://github.com/moby/moby/blob/master/pkg/namesgenerator/...
- Docker Inc. refuses to patch HIGH vulnerabilities in Docker
-
Do not install Docker Desktop on GNU/Linux systems
Try to use moby instead since that is the engine in Docker.
https://github.com/moby/moby
-
Exploring Podman: A More Secure Docker Alternative
> Podman is designed to help with this by providing stronger default security settings compared to Docker. Features like rootless containers, user namespaces, and seccomp profiles, while available in Docker, aren't enabled by default and often require extra setup.
Seccomp has been enabled by default since 2015: https://github.com/moby/moby/pull/18780
It is true that Rootless isn't enabled by default but its "extra setup" can be done with a single command (`dockerd-rootless-setuptool.sh install`)
- Moby: Block io_uring_* syscalls in default profile
- Io_uring will be blocked by default on Docker
-
OpenZFS 2.2: Block Cloning, Linux Containers, BLAKE3
Perhaps.
Thing is, https://github.com/moby/moby/blob/670bc0a46c4ca03b75f1e72f73... is using https://github.com/mistifyio/go-zfs which features code like `out, err := zfsOutput("get", "-H", key, d.Name)` (Source: https://github.com/mistifyio/go-zfs/blob/master/zfs.go#L315) to get a single zfs property.
Somebody chose to use a library as abstraction that looks good but is implemented as a MVP (nothing wrong with that). "In the future, we hope to work directly with libzfs" should have raised an alarm somewhere, though.
-
The Twelve-Factor App
AppArmor can restrict /proc and this is even used by docker: https://github.com/moby/moby/blob/master/contrib/apparmor/te...
What are some alternatives?
staticcheck
podman - Podman: A tool for managing OCI containers and pods.
goimports - [mirror] Go Tools
containerd - An open and reliable container runtime
go-checkstyle - checkstyle for go
nerdctl - contaiNERD CTL - Docker-compatible CLI for containerd, with support for Compose, Rootless, eStargz, OCIcrypt, IPFS, ...
gosimple
docker-openwrt - OpenWrt running in Docker
errcheck - errcheck checks that you checked errors.
ofelia - A docker job scheduler (aka. crontab for docker)
Go Metalinter
k3d - Little helper to run CNCF's k3s in Docker