runtime-tools
golang-standards/project-layout
runtime-tools | golang-standards/project-layout | |
---|---|---|
4 | 195 | |
416 | 45,978 | |
1.2% | 1.3% | |
3.3 | 6.4 | |
8 months ago | about 2 months ago | |
Go | Makefile | |
Apache License 2.0 | GNU General Public License v3.0 or later |
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.
runtime-tools
-
Podman/buildah oci bundle
But there is another issue - machinectl doesn't know how to start oci-bundle. It would be nice to have a tool which would generate .nspawn file from config.json (apparrently, there is an open issue for that https://github.com/opencontainers/runtime-tools/issues/669)
-
Youki, a container runtime in Rust, passed all the default tests provided by opencontainers.
I think you might be looking at the gitignore for https://github.com/opencontainers/runtime-tools/blob/master/.gitignore , which is NOT the repo made by /u/utam0k. That's a large repo from opencontainers that includes many different things, so that .gitignore is bigger but by no means unreasonable.
youki, a container runtime in Rust I'm implementing, passed all the default tests provided by opencontainers. There are still many issues that need to be implemented, but it's getting fun. I think Rust to be a good choice for implementing container utilities. If you are interested, please refer to the motivation section of README for more details. I'd like to hear your opinions.
-
Crun: Fully featured OCI runtime and C library for running containers
crun runs the OCI validations tests on each PR.
The tests are maintained here: https://github.com/opencontainers/runtime-tools/tree/master/...
I guess this is the closest to be "certified compliant", but that is not enough for working with existing container engines as everyone just assumes runc is used
golang-standards/project-layout
-
The power of the CLI with Golang and Cobra CLI
cmd: here where we will leave the main.go that starts our app.
-
What's your go to literature to build Go libraries?
> https://github.com/golang-standards/project-layout
The name of the repo is really and intentionally misleading. rsc filled an issue there to point this out, but the repo maintainer just disabled issues altogether so now no one can see it.
Even when it would not have such parasitic name, many seasoned Go programmers, me included, consider the self-proclaimed "Standard Go project Layout" as the opposite of what is good and advisable.
Unfortunately, the name just works, so it is being recommended all over the Internet since its inception.
-
"14 Years of Go" by Rob Pike
Your comment makes it look as if you're saying you hate the Go development team, but it seems that isn't the case.
I get a little of what you're saying, I wouldn't say I hate anyone, but I strongly dislike how a lot of projects are organized. I think a lot stems from https://github.com/golang-standards/project-layout , which pretended to be standard and was so (ab)used one of the creators opened an issue about it. If you look at the actual Go src, it's much, much cleaner.
-
Looking for elegant code bases written in GoLang
So you don't get blind sided for self proclaimed "standards" that are not
- I'm coming from Java and I have been told that I'm writing go like I'm writing Java. Basically creating structs, injecting fields, and attaching methods. What else can I do?
- O poder do CLI com Golang e Cobra CLI
- Como deixar o Swagger com tema dark mode usando Swaggo e Golang
-
Can I point a module to a subdirectory?
I am writing a project that has two components: a CLI and a library. I've organised the project as follows (as per organisation instructions):
-
How To Build A Containerized Microservice in Golang: A Step-by-step Guide with Example Use-Case
Familiarity with the standard Golang project structure, which you can find here.
-
Building RESTful API with Hexagonal Architecture in Go
I've been learning how to build web applications using different frameworks and languages for a while now, such as Laravel with its MVC architecture and Node.js following the 'Hapi.js Way'. As I'm trying to create a new portfolio project using Go, I found myself contemplating over the ideal project structure. I wanted something that not only aligns with the standard Go project layout, but also makes the code both easy to write and understand. That's when I stumbled upon the concept of Hexagonal Architecture, as showcased in Netflix's engineering blog. The idea of seamlessly swapping infrastructures with minimal code changes fascinated me, and I decided to implement it in my new project.
What are some alternatives?
crun - A fast and lightweight fully featured OCI runtime and C library for running containers
uber-go-style-guide-kr - Uber's Go Style Guide Official Translation in Korean. Linked to the uber-go/guide as a part of contributions
singularity - Singularity has been renamed to Apptainer as part of us moving the project to the Linux Foundation. This repo has been persisted as a snapshot right before the changes.
modern-go-application - Modern Go Application example
umoci - umoci modifies Open Container images
uber-go-style-guide-th - Uber's Go Style Guide Translation in Thai. Linked to the uber-go/guide as a part of contributions https://github.com/uber-go/guide
image-tools - OCI Image Tooling
go-restful-api - An idiomatic Go REST API starter kit (boilerplate) following the SOLID principles and Clean Architecture
youki - An experimental container runtime written in Rust
cookiecutter-golang - A Go project template
runtime-spec - OCI Runtime Specification
service - Starter-kit for writing services in Go using Kubernetes.