godotenv
kin-openapi
Our great sponsors
godotenv | kin-openapi | |
---|---|---|
17 | 6 | |
7,526 | 2,372 | |
- | 3.5% | |
3.7 | 8.4 | |
about 1 month ago | 7 days ago | |
Go | Go | |
MIT License | MIT License |
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.
godotenv
-
Autenticação com Golang e AWS Cognito
Primeiro vamos carregar nossas envs com o pacote godotenv, depois iniciamos nosso cognito client, passando o COGNITO_CLIENT_ID, que pegamos anteriormente, depois iniciamos o gin e criamos um server, isso é o suficiente.
-
Tools besides Go for a newbie
IDE: use whatever make you productive. I personally use vscode. VCS: git, as golang communities use github heavily as base for many libraries. AFAIK Linter: use staticcheck for linting as it looks like mostly used linting tool in go, supported by many also. In Vscode it will be recommended once you install go plugin. Libraries/Framework: actually the standard libraries already included many things you need, decent enough for your day-to-day development cycles(e.g. `net/http`). But here are things for extra: - Struct fields validator: validator - Http server lib: chi router , httprouter , fasthttp (for non standard http implementations, but fast) - Web Framework: echo , gin , fiber , beego , etc - Http client lib: most already covered by stdlib(net/http), so you rarely need extra lib for this, but if you really need some are: resty - CLI: cobra - Config: godotenv , viper - DB Drivers: sqlx , postgre , sqlite , mysql - nosql: redis , mongodb , elasticsearch - ORM: gorm , entgo , sqlc(codegen) - JS Transpiler: gopherjs - GUI: fyne - grpc: grpc - logging: zerolog - test: testify , gomock , dockertest - and many others you can find here
-
Reading Environment Variable from a .env file on a Server
In his code it is done using https://github.com/joho/godotenv
- Libraries you use most of your projects?
-
Restful API with Golang practical approach
envconfig: Library for managing configuration data from environment variables (https://github.com/joho/godotenv)
-
Is this clear why its useful?
There is already a more complete, safer and neatly written godotenv alternative. It may be taken as an educational inspiration for next attempts.
-
I need some help setting up variables for the sake of my sanity
Chances are you are going to set them in you real server, and most likely you will going to use Linux for that. So for local development create a .env file with those in there. And at the start of you program, load them. You can use https://github.com/joho/godotenv Don’t share that file of course, and don’t put it in git.
-
How can I "source" a bash script?
Maybe https://github.com/joho/godotenv can help
-
passwords, secrets, keys - best practice
joho/godotenv
- I'm looking for a good alternativ to Viper
kin-openapi
-
Create Production-Ready SDKs With gRPC Gateway
We'll use the excellent kin-openapi Go library to convert the OpenAPI 2.0 schema to OpenAPI 3.0.
-
OpenAPI Generator allows generation of API client libraries from OpenAPI Specs
What is your language?
I've found kin-openapi to be good for Go:
https://github.com/getkin/kin-openapi
-
swaggo/swag alternative, but should generate OpenAPI 3.0 spec file
I recently used https://github.com/getkin/kin-openapi openapi2 and openapi2conv to convert the v2 yaml to v3 yaml.
-
Any good OpenAPI 3.x spec generator for a Go REST API?
This might not be very helpful, but I've have found every "generate spec from code" package to be limited sooner or later, and that's across languages. I finally settled on writing the spec file by hand, linting it in CI using openapi-cli, and using kin-openapi in Go tests to ensure responses match their schema.
-
What are your favorite packages to use?
oklog/ulid to generate IDs. coreos/go-oidc for validating JWTs I get from auth. google/go-cmp for comparing structs in tests (unless the project is already using Testify). spf13/pflag because life's too short for Go's flag handling. getkin/kin-openapi for validating reqests/responses against my OpenAPI spec (in tests).
-
Do you use swagger to generate backends?
Then define the corresponding YAML/JSON specification (again manually) either using Swagger 2.0 (with go-swagger) or OpenAPI 3 (with kin-openapi), and
What are some alternatives?
viper - Go configuration with fangs
GoSwagger - Swagger 2.0 implementation for go
gotenv - Load environment variables from `.env` or `io.Reader` in Go.
chi - lightweight, idiomatic and composable router for building Go HTTP services
structs - Golang struct operations.
oapi-codegen - Generate Go client and server boilerplate from OpenAPI 3 specifications
xferspdy - Xferspdy provides binary diff and patch library in golang. [Mentioned in Awesome Go, https://github.com/avelino/awesome-go]
Gin - Gin is a HTTP web framework written in Go (Golang). It features a Martini-like API with much better performance -- up to 40 times faster. If you need smashing performance, get yourself some Gin.
delve - Delve is a debugger for the Go programming language.
swagger2markup - A Swagger to AsciiDoc or Markdown converter to simplify the generation of an up-to-date RESTful API documentation by combining documentation that’s been hand-written with auto-generated API documentation.
fzf - :cherry_blossom: A command-line fuzzy finder
openapi-generator - OpenAPI Generator allows generation of API client libraries (SDK generation), server stubs, documentation and configuration automatically given an OpenAPI Spec (v2, v3)