Go Fiber를 사용하여 RESTful API 구축: Express에서 영감을 받은 상용구-Golang-php.cn

Building a RESTful API with Go Fiber: An Express-Inspired Boilerplate
A boilerplate/starter project for quickly building RESTful APIs using Go, Fiber, and PostgreSQL. Inspired by the Express boilerplate.

The app comes with many built-in features, such as authentication using JWT and Google OAuth2, request validation, unit and integration tests, docker support, API documentation, pagination, etc. For more details, check the features list below.

Features
Commands
Environment Variables
Project Structure
API Documentation
Error Handling
Validation
Authentication
Authorization
Logging
Linting
Contributing

Features

SQL database: PostgreSQL Object Relation Mapping using Gorm
Database migrations: with golang-migrate
Validation: request data validation using Package validator
Logging: using Logrus and Fiber-Logger
Testing: unit and integration tests using Testify and formatted test output using gotestsum
Error handling: centralized error handling mechanism
API documentation: with Swag and Swagger
Sending email: using Gomail
Environment variables: using Viper
Security: set security HTTP headers using Fiber-Helmet
CORS: Cross-Origin Resource-Sharing enabled using Fiber-CORS
Compression: gzip compression with Fiber-Compress
Docker support
Linting: with golangci-lint

Commands

Clone the repo:


git clone --depth 1 https://github.com/indrayyana/go-fiber-boilerplate.git
cd go-fiber-boilerplate
rm -rf ./.git

로그인 후 복사

Install the dependencies:


go mod tidy

로그인 후 복사

Set the environment variables:


cp .env.example .env

# open .env and modify the environment variables (if needed)

로그인 후 복사

Running locally:


make start

로그인 후 복사

Or running with live reload:

air

로그인 후 복사

Note:
Make sure you have Air installed.
See ? How to install Air

Testing:


# run all tests
make tests

# run all tests with gotestsum format
make testsum

# run test for the selected function name
make tests-TestUserModel

로그인 후 복사

Docker:


# run docker container
make docker

# run all tests in a docker container
make docker-test

로그인 후 복사

Linting:


# run lint
make lint

로그인 후 복사

Swagger:


# generate the swagger documentation
make swagger

로그인 후 복사

Migration:


# Create migration
make migration-<table-name>

# Example for table users
make migration-users

로그인 후 복사


# run migration up in local
make migrate-up

# run migration down in local
make migrate-down

# run migration up in docker container
make migrate-docker-up

# run migration down all in docker container
make migrate-docker-down

로그인 후 복사

Environment Variables

The environment variables can be found and modified in the .env file. They come with these default values:


# server configuration
# Env value : prod || dev
APP_ENV=dev
APP_HOST=0.0.0.0
APP_PORT=3000

# database configuration
DB_HOST=postgresdb
DB_USER=postgres
DB_PASSWORD=thisisasamplepassword
DB_NAME=fiberdb
DB_PORT=5432

# JWT
# JWT secret key
JWT_SECRET=thisisasamplesecret
# Number of minutes after which an access token expires
JWT_ACCESS_EXP_MINUTES=30
# Number of days after which a refresh token expires
JWT_REFRESH_EXP_DAYS=30
# Number of minutes after which a reset password token expires
JWT_RESET_PASSWORD_EXP_MINUTES=10
# Number of minutes after which a verify email token expires
JWT_VERIFY_EMAIL_EXP_MINUTES=10

# SMTP configuration options for the email service
SMTP_HOST=email-server
SMTP_PORT=587
SMTP_USERNAME=email-server-username
SMTP_PASSWORD=email-server-password
EMAIL_FROM=support@yourapp.com

# OAuth2 configuration
GOOGLE_CLIENT_ID=yourapps.googleusercontent.com
GOOGLE_CLIENT_SECRET=thisisasamplesecret
REDIRECT_URL=http://localhost:3000/v1/auth/google-callback

로그인 후 복사

Project Structure


src\
 |--config\         # Environment variables and configuration related things
 |--controller\     # Route controllers (controller layer)
 |--database\       # Database connection & migrations
 |--docs\           # Swagger files
 |--middleware\     # Custom fiber middlewares
 |--model\          # Postgres models (data layer)
 |--response\       # Response models
 |--router\         # Routes
 |--service\        # Business logic (service layer)
 |--utils\          # Utility classes and functions
 |--validation\     # Request data validation schemas
 |--main.go         # Fiber app

로그인 후 복사

API Documentation

To view the list of available APIs and their specifications, run the server and go to http://localhost:3000/v1/docs in your browser.

Building a RESTful API with Go Fiber: An Express-Inspired Boilerplate

This documentation page is automatically generated using the Swag definitions written as comments in the controller files.

See ? Declarative Comments Format.

API Endpoints

List of available routes:

Auth routes:\
POST /v1/auth/register - register\
POST /v1/auth/login - login\
POST /v1/auth/logout - logout\
POST /v1/auth/refresh-tokens - refresh auth tokens\
POST /v1/auth/forgot-password - send reset password email\
POST /v1/auth/reset-password - reset password\
POST /v1/auth/send-verification-email - send verification email\
POST /v1/auth/verify-email - verify email\
GET /v1/auth/google - login with google account

User routes:\
POST /v1/users - create a user\
GET /v1/users - get all users\
GET /v1/users/:userId - get user\
PATCH /v1/users/:userId - update user\
DELETE /v1/users/:userId - delete user

Error Handling

The app includes a custom error handling mechanism, which can be found in the src/utils/error.go file.

It also utilizes the Fiber-Recover middleware to gracefully recover from any panic that might occur in the handler stack, preventing the app from crashing unexpectedly.

The error handling process sends an error response in the following format:


{
  "code": 404,
  "status": "error",
  "message": "Not found"
}

로그인 후 복사

Fiber provides a custom error struct using fiber.NewError(), where you can specify a response code and a message. This error can then be returned from any part of your code, and Fiber's ErrorHandler will automatically catch it.

For example, if you are trying to retrieve a user from the database but the user is not found, and you want to return a 404 error, the code might look like this:


func (s *userService) GetUserByID(c *fiber.Ctx, id string) {
    user := new(model.User)

    err := s.DB.WithContext(c.Context()).First(user, "id = ?", id).Error

    if errors.Is(err, gorm.ErrRecordNotFound) {
        return fiber.NewError(fiber.StatusNotFound, "User not found")
    }
}

로그인 후 복사

Validation

Request data is validated using Package validator. Check the documentation for more details on how to write validations.

The validation schemas are defined in the src/validation directory and are used within the services by passing them to the validation logic. In this example, the CreateUser method in the userService uses the validation.CreateUser schema to validate incoming request data before processing it. The validation is handled by the Validate.Struct method, which checks the request data against the schema.


import (
    "app/src/model"
    "app/src/validation"

    "github.com/gofiber/fiber/v2"
)

func (s *userService) CreateUser(c *fiber.Ctx, req validation.CreateUser) (*model.User, error) {
    if err := s.Validate.Struct(&req); err != nil {
        return nil, err
    }
}

로그인 후 복사

Authentication

To require authentication for certain routes, you can use the Auth middleware.


import (
    "app/src/controllers"
    m "app/src/middleware"
    "app/src/services"

    "github.com/gofiber/fiber/v2"
)

func SetupRoutes(app *fiber.App, u services.UserService, t services.TokenService) {
  userController := controllers.NewUserController(u, t)
    app.Post("/users", m.Auth(u), userController.CreateUser)
}

로그인 후 복사

These routes require a valid JWT access token in the Authorization request header using the Bearer schema. If the request does not contain a valid access token, an Unauthorized (401) error is thrown.

Generating Access Tokens:

An access token can be generated by making a successful call to the register (POST /v1/auth/register) or login (POST /v1/auth/login) endpoints. The response of these endpoints also contains refresh tokens (explained below).

An access token is valid for 30 minutes. You can modify this expiration time by changing the JWT_ACCESS_EXP_MINUTES environment variable in the .env file.

Refreshing Access Tokens:

After the access token expires, a new access token can be generated, by making a call to the refresh token endpoint (POST /v1/auth/refresh-tokens) and sending along a valid refresh token in the request body. This call returns a new access token and a new refresh token.

A refresh token is valid for 30 days. You can modify this expiration time by changing the JWT_REFRESH_EXP_DAYS environment variable in the .env file.

Authorization

The Auth middleware can also be used to require certain rights/permissions to access a route.


import (
    "app/src/controllers"
    m "app/src/middleware"
    "app/src/services"

    "github.com/gofiber/fiber/v2"
)

func SetupRoutes(app *fiber.App, u services.UserService, t services.TokenService) {
  userController := controllers.NewUserController(u, t)
    app.Post("/users", m.Auth(u, "manageUsers"), userController.CreateUser)
}

로그인 후 복사

In the example above, an authenticated user can access this route only if that user has the manageUsers permission.

The permissions are role-based. You can view the permissions/rights of each role in the src/config/roles.go file.

If the user making the request does not have the required permissions to access this route, a Forbidden (403) error is thrown.

Logging

Import the logger from src/utils/logrus.go. It is using the Logrus logging library.

Logging should be done according to the following severity levels (ascending order from most important to least important):


import "app/src/utils"

utils.Log.Panic('message') // Calls panic() after logging
utils.Log.Fatal('message'); // Calls os.Exit(1) after logging
utils.Log.Error('message');
utils.Log.Warn('message');
utils.Log.Info('message');
utils.Log.Debug('message');
utils.Log.Trace('message');

로그인 후 복사