ko VS kelseyhightower/envconfig

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

To configure the app I'd take a look at https://github.com/kelseyhightower/envconfig

envconfig

- Having one way of configuring the app is excellent. You can either prefer environment variables, a file, or flags. You can do what Viper does by reading the file and unmarshalling it. The built-in flag package is enough for your flag-based config needs. If you want to prefer environment variables, I prefer https://github.com/kelseyhightower/envconfig

To extract values from the system environment, I utilize envconfig, a Go package. Envconfig facilitates mapping system environment variables to a Go struct. These Go structs are exposed through a config package, enabling other parts of the application to access them.

You could prefix your env vars and use this package. https://github.com/kelseyhightower/envconfig

kelseyhightower/envconfig

Pretty much all of our services and pkgs use https://github.com/kelseyhightower/envconfig. It’s dead simple, gets out of your way, and is battle tested

https://github.com/kelseyhightower/envconfig (read config from environment variables, more succinct than viper)