gaming-store

The GOOFR digital games store.

Development

The following section focuses on the development part of the project, including prerequisites, how to build and run the code, and how to contribute.

Table of Contents

• Prerequisites
  • Web App
  • Server App
  • Docker
  • GNU Make
• Applications
  • Quick Start
  • Web App
  • Server App
• Contributing

Prerequisites

Web App

The web application runs on Node.js version 20.

Install the dependencies inside the web directory with:

npm install

Server App

The server application is written in Go and uses the version 1.23.

Docker

To run the application in containers, the Docker Engine is expected to be installed.

GNU Make

To ensure a smooth development process, we use GNU Make to run all necessary commands for building, testing, and deploying this project. Make files help automate these tasks, making it easier to manage complex dependencies and workflows. By using GNU Make, we can maintain consistency across different environments and streamline our development efforts.

GCP Service Account

To enable the file upload functionality in this project, a Google Cloud Platform (GCP) service account key is required. The service account must have the Storage Object Admin role assigned, which grants the necessary permissions to upload files to a GCP Cloud Storage bucket. Ensure that the JSON key file for the service account is properly configured in the application settings to authenticate.

To run the server with the file upload functionality using the Dockerfile, it is necessary to have the JSON key file in the server directory, named gcp-key.json.

Applications

Quick Start

In the project root directory, there is a Makefile that contains some targets to help develop and build the web and server applications.

Build and run both applications in a Docker container:

make up

---

Or, if the goal is to run each application independently, see the following steps.

1. Start the web application in a development context:

   make dev-web

2. Update the server configuration file, especially regarding the database connection string

   • To run the database locally, use the Docker Compose file:

     docker compose up database

3. Start the server application in a development context:

   make dev-server

Web App

The web application can be found in the web directory. It uses React.

The web application contains several scripts to lint, build and run the project. To check the available scripts, run the following command inside the web directory:

npm run

Server App

The server application can be found in the server directory. It contains the Go code that serves the following routes:

Route	Description
/	Web Application
/api	REST API
/api/docs/ui	Swagger UI

The server contains a Makefile that defines a set of tasks that can be run to help with development. The available targets can be checked by running the following command inside the server directory:

make help

To serve the web application, the server expects the web static files to be in the dist/web directory.

The REST API is documented in a Swagger Specification file (api.yml) in the api/swagger directory. This file is also used by the server to generate the API models and server boilerplate code to handle the HTTP API (see the generate.go file).

Inside the api/swagger directory, there is also a ui folder that contains the Swagger UI that is served by the server to present the REST API documentation. See the README.md file in api/swagger for more information.

The server application requires a PostgreSQL database to manipulate the persistent data. There is a Docker Compose file (docker-compose.yml) in the project root directory that already contains a database service that can be run locally.

The database migrations can be found in database/migrations in the server directory. When the server starts, it will make sure that the database is running the configured migration version. This behavior can also be configured and disabled if necessary.

Note that there is a configuration file in the server directory that contains some placeholder variables that allow the server to be configured. By default, the server reads the config.yml file, but this can be overridden by setting the CONFIG_FILE environment variable with a path to a valid configuration file in any other directory.

Contributing

Branches

• The main branch contains the production code
• To develop a new feature or fix a bug, a new branch should be created based on the main branch

Issues

• The features and bugs should exist as a GitHub issue with an appropriate description
• The status of the issues can be seen in the associated GitHub project

Commits

• Git commits should follow conventional commits

Pull Requests

• To merge the code into production, a pull request should be opened following the existing template to describe it, as well as the appropriate labels
• To merge the pull request, the code must pass all GitHub action checks, be approved by at least one of the code owners, and be squashed and merged

Deployments

• After the code is merged into the main branch, there is a GitHub action that automatically builds and deploys the code to production

Releases

• To release a new version of the project, semantic versioning should be followed