ko VS Gogs

Apko leverages the APK package format from Alpine and draws inspiration from ko, a fast container image builder for Go applications.

- There're many resources available about containerizing an application, but I suggest you buildpacks or ko, which doesn't require writing a Dockerfile

ko

You don't need to write and manage Dockerfiles. Simply just use ko: https://github.com/google/ko (You also don't need Docker Engine)

Or don't write a Dockerfile at all, and use ko: https://github.com/google/ko

Here is link number 1 - Previous text "ko"

It depends on your use case, but have you ever tried google/ko?

If you're using Go, I recommend https://github.com/google/ko (shameless plug), or for Java, use Jib.

I would recommend Google Ko if you are packaging Go apps: https://github.com/google/ko

> Gitea but the other one

Wouldn't that also be Gogs? https://gogs.io/

I remember when that one was what a lot of people were looking into, before the Gitea fork happened. It's odd to see how this has happened yet again, but I guess is a good thing that it's even possible in the first place, if there are indeed differing values and goals?

Gogs - A self-hosted Git service. [Git]

Golang has a ton of single binary websites out there. The two that come to mind off hand are Gogs/Gitea only because I contributed to them

https://github.com/gogs/gogs

https://github.com/go-gitea/gitea

I did use https://gogs.io/ in the past. Was nice.

This reminds me of Gogs [0], where the original author refused a lot of good ideas and improvements, eventually leading to a fork [1] that's now a lot more popular and active than the original.

[0] https://gogs.io/

[1] https://gitea.io/en-us/

To me i like the best GOGS https://gogs.io/. Same features like GitHub but all local and lightweight

Gogs (https://gogs.io/)