If you are talking about local development this is where dotenv files have been helpful. You could always exec `DEVELOPMENT=true go run .`
If you are talking about local development this is where dotenv files have been helpful. You could always exec `DEVELOPMENT=true go run .`
Alternatively, you could use a Cloudflare Workers as a proxy to your Go backend. In my setup Pages will deploy the functions and it operates as a BFF.
Alternatively, you could use a Cloudflare Workers as a proxy to your Go backend. In my setup Pages will deploy the functions and it operates as a BFF.
I’ve also used Containerfiles and --target to execute a single step. This enables reuse between the dev and CI.
I’ve also used Containerfiles and --target to execute a single step. This enables reuse between the dev and CI.
Currently I’m using it in a private project, but will get the example working today.
Currently I’m using it in a private project, but will get the example working today.
With Postgres I get ACID compliance and key-value with JSONB.
With Postgres I get ACID compliance and key-value with JSONB.
So it just depends on your production reqs and team size.
So it just depends on your production reqs and team size.