Zaine Arch aa31cc37d9
All checks were successful
Build Org Backend / build (push) Successful in 12s
auth
2026-05-09 00:36:49 +01:00
2026-05-08 23:57:56 +01:00
2026-05-08 23:35:55 +01:00
FIx
2026-05-09 00:08:32 +01:00
FIx
2026-05-09 00:08:32 +01:00
2026-05-09 00:36:49 +01:00
2026-05-08 23:35:55 +01:00
2026-05-08 23:35:55 +01:00
2026-05-08 23:46:34 +01:00
2026-05-09 00:36:49 +01:00

Introduction

This repository contains the source code and documentation for all of my APIs. It serves as a centralised location for my self-hosted services to use.

Structure

The repository is organised into the following main directories:

Deployment

The main branch build is controlled by .gitea/workflows/build.yml. On a successful build it packages the Spring Boot jar, installs the project-owned misc/org-backend.service unit into systemd, reloads systemd, enables the service, and restarts it.

The service runs the stable build artifact at:

/home/zaine/master-folder/projects/java_projects/org_backend/target/org-backend.jar

Runtime configuration is loaded by systemd from:

/etc/org-backend/org-backend.env

Create that file once on the server with the production values required by the app. The Gitea deploy step verifies that it exists, but it does not create or overwrite it.

Use /api/auth/register to create users and /api/auth/login to receive a JWT. Protected API routes send that token as:

Authorization: Bearer <token>

The live systemd unit at /etc/systemd/system/org-backend.service is managed as a symlink to misc/org-backend.service, so the project copy is the source of truth.

Description
No description provided
Readme 3.5 MiB
Languages
Java 98.4%
Shell 1%
Makefile 0.3%
Dockerfile 0.3%