2020-08-14
3079
#docker#go#postgresql
Michael Okoko
23212
Aug 14, 2020 ⋅ 10 min read

How to build a RESTful API with Docker, PostgreSQL, and go-chi

Michael Okoko Linux and Sci-Fi ➕ = ❤️

Recent posts:

improving ux with scroll-select box

How to improve UX with a scroll-select box

The scroll-select box is a great tool for frontend developers to improve the user experience of their applications. Learn how to build a scrollable date picker that mimics the iOS style, but with the exemption of the <select> element.

Emmanuel Odioko
Feb 7, 2025 ⋅ 10 min read
Deploying Next.js apps with Deno Deploy

Deploying Next.js apps with Deno Deploy

For those just getting started with deploying their first application, Deno Deploy’s simplicity might be exactly what you need; no complex configuration files to wrestle with or cloud concepts to master before getting your app live.

Emmanuel Odioko
Feb 6, 2025 ⋅ 5 min read
A Guide To Object.groupBy: An Alternative To Array.reduce

A guide to Object.groupBy: An alternative to Array.reduce

Learn how Object.groupBy and Map.groupBy improve JavaScript data grouping over reduce, with performance benchmarks and comparisons.

Sebastian Weber
Feb 5, 2025 ⋅ 4 min read
Best CI/CD tools for React Native

Best CI/CD tools for React Native

Get a high-level comparison of five of the most popular and well-used CI/CD tools for React Native apps, including the features they support.

Hussain Arif
Feb 5, 2025 ⋅ 7 min read
View all posts

4 Replies to "How to build a RESTful API with Docker, PostgreSQL, and go-chi"

  1. Superb article. Basically answered my question as regards persisting the db object for the lifetime of the application without any drawbacks.

  2. Nice article! Thanks for helping me to bootstrap this nice little service, I love it. Just a small adjust that I needed to do:
    – the service is reporting this log to all the calls: `http: superfluous response.WriteHeader call from github.com/go-chi/render.JSON (responder.go:104)`

    I found that it happens because of the line: `w.WriteHeader(405)` and `w.WriteHeader(400)` inside the functions: `methodNotAllowedHandler` and `notFoundHandler`; removing these two lines fixed the issue; and actually we are returning the proper status code because of the errors values inside the `handler/errors.go` file, so no harm done by removing these lines.

Leave a Reply