Go Restful API Boilerplate

Easily extendible RESTful API boilerplate aiming to follow idiomatic go and best practice.

The goal of this boiler is to have a solid and structured foundation to build upon on.

Any feedback and pull requests are welcome and highly appreciated. Feel free to open issues just for comments and discussions.

Features

The following feature set is a minimal selection of typical Web API requirements:

• Configuration using viper
• CLI features using cobra
• PostgreSQL support including migrations using go-pg
• Structured logging with Logrus
• Routing with chi router and middleware
• JWT Authentication using lestrrat-go/jwx with example passwordless email authentication
• Request data validation using ozzo-validation
• HTML emails with go-mail

Start Application

• Clone and change into this repository

Local

• Create a postgres database and set environment variables for your database accordingly if not using below defaults
• Run the application to see available commands: go run main.go
• Run all migrations from database/migrate folder: go run main.go migrate
• Run the application with command serve: go run main.go serve

Using Docker Compose

• First start the database only: docker compose up -d postgres
• Once initialize the database by running all migrations in database/migrate folder: docker compose exec server ./main migrate
• Start the api server: docker compose up server

API Routes

Authentication

For passwordless login following routes are available:

Example API

Besides /auth/_ the API provides two main routes /api/_ and /admin/*, as an example to separate application and administration context. The latter requires to be logged in as administrator by providing the respective JWT in Authorization Header.

Check routes.md for a generated overview of the provided API routes.

Client API Access and CORS

The server is configured to serve a Progressive Web App (PWA) client from ./public folder (this repo only serves an example index.html, see below for a demo PWA client to put here). In this case enabling CORS is not required, because the client is served from the same host as the api.

If you want to access the api from a client that is serverd from a different host, including e.g. a development live reloading server with below demo client, you must enable CORS on the server first by setting environment variable ENABLE_CORS=true on the server to allow api connections from clients serverd by other hosts.

Demo client application

For demonstration of the login and account management features this API serves a demo Vue.js PWA. The client's source code can be found here. Build and put it into the api's ./public folder, or use the live development server (requires CORS enabled).

Outgoing emails containing the login token will be print to stdout if no valid email smtp settings are provided by environment variables (see table below). If EMAIL_SMTP_HOST is set but the host can not be reached the application will exit immediately at start.

Use one of the following bootstrapped users for login:

• admin@boot.io (has access to admin panel)
• user@boot.io

A deployed version can also be found on Heroku

Testing

Package auth/pwdless contains example api tests using a mocked database. Run them with: go test -v ./...

Environment Variables

By default viper will look at $HOME/.go-base.yaml for a config file. Setting your config as Environment Variables is recommended as by 12-Factor App.