The official restful application programming interface of helpwave

helpwave team members may read up on best practices and additional onboarding material in the internal wiki

A .env.example file is provided and can be used to customize the server. copy the file to .env and edit it to your needs.

cp .env.example .env

Use the docker-compose.prod.yml as an example configuration for production purposes.

Use

docker-compose up -d --build

to build the docker image and start all necessary services.

Your backend will listen at https://localhost:3000/. If you want to test your endpoints you can use swagger.

Run Docker Compose to start the Database:

docker compose up -d postgres

the database will appear on port 5432 on your host. If you want to remove the database:

docker compose down -v postgres

This project uses Golang version 1.19.1, the latest version available at the time of writing.

You can build the project using

go build rest-api

and run it using

go run rest-api

The webserver will listen on https://localhost:3000

go build

will produce a single binary in the root called "rest-api".

Note: Release builds should be versioned, please compile them using go build -ldflags="-X main.Version=<version>" .

This project supports Git Hooks. Primarily to lint the commit message. To use our hooks, execute the following.

make githooks

During Development the server will fall back to a default key pair, to generate a keypair for production use you can leverage openssl:

openssl ecparam -name prime256v1 -genkey -noout -out jwt-private.pem &&
openssl ec -in jwt-private.pem -pubout -out jwt-public.pem

We use gin for routing.

This project uses swaggo to generate openapi specifications. First install the swag cli using:

go install github.com/swaggo/swag/cmd/swag@latest

Now you can run swag init to update /docs. The server will serve the specification on /swagger/index.html (just /swagger won't work).

To add a route use the declarative comments format.

To connect to postgres we use GORM.

Keep in mind the following conventions:

GORM prefers convention to configuration, by default, GORM uses ID as primary key, pluralize struct name to snake_cases as table name, snake_case as column name, and uses CreatedAt, UpdatedAt to track creating/updating time

Install the migrate cli using:

go install -tags 'postgres' github.com/golang-migrate/migrate/v4/cmd/migrate@latest

New migrations can be generated using migrate create -ext sql -dir db/migrations -seq <title>.

We provide mock data as data/mocks.sql. When you use the development docker compose setup, it will be automatically inserted.

Users with bash installed can use

./migration.sh up

to run a migration against the db specified in .env.

Code scanning is a feature of GitHub that can be used to analyze the code. This helps in the search for security vulnerabilities and programming errors.

The go application will be build by GitHub actions,
afterwards a docker image is build and pushed to the GitHub container registry

The following docker image tags exist:

• branch-xxx, where xxx is the branch name
• edge for the main branch
• latest for the latest tag / release
• v1, v1.0, v1.0.0 for the matching tags

Make sure to prefix the tags with v if you wan't a image for them, I suggest matching the format: v\d+\.\d+\.\d+ (Examples: v1.0.0, v14.15.161, ...)

I suggest creating new releases using the GitHub actions workflow. The primary advantage is, that the release is made by github-actions and the helpwave artifact is included.

Afterwards you should adjust the title (which is the tag name by default) / description of the release.