No description
  • TypeScript 97.2%
  • Shell 2.4%
  • CSS 0.3%
  • HTML 0.1%
Find a file
Olivier 128ba89919
All checks were successful
Quatrain CoreApps Sovereign CI / Build Containers & Validate Monorepo (push) Successful in 1m25s
Quatrain CoreApps Sovereign CI / Build Containers & Validate Monorepo (pull_request) Successful in 1m25s
Publish Studio Image Container / Build & Push Studio Image to qtrn.io (push) Successful in 1m19s
chore: remove packages/ symlinks to Core and CoreUX sources
The packages/ entries were symlinks to absolute paths on one developer
machine, dangling in every other checkout. Dependencies already resolve
through the portal: resolutions and the studio-web Vite aliases point at
../../../Core and ../../../CoreUX directly, so nothing references them.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-11 08:04:58 +01:00
.forgejo/workflows ci(forgejo): publish container images for linux/arm64 only 2026-11-10 21:30:29 +01:00
.tycho chore: make Forgejo the source of authority, GitHub a read-only mirror 2026-11-10 19:34:42 +01:00
.yarn/releases feat: initialize studio apps and CLI workspace with supporting infrastructure and bookstore example 2026-05-25 12:10:02 +02:00
apps chore: remove packages/ symlinks to Core and CoreUX sources 2026-11-11 08:04:58 +01:00
assets refactor: restructure workspace paths for Core and CoreUI packages, add assets, and update build scripts 2026-05-25 19:44:29 +02:00
bin docs: explain why container images target arm64 only 2026-11-10 21:30:54 +01:00
containers chore: make Forgejo the source of authority, GitHub a read-only mirror 2026-11-10 19:34:42 +01:00
examples/bookstore refactor: update CoreUI and package ui* dependency references to CoreUX and ux* 2026-06-02 23:31:27 +02:00
.dockerignore feat: initialize studio apps and CLI workspace with supporting infrastructure and bookstore example 2026-05-25 12:10:02 +02:00
.gitignore refactor: remove legacy migration schema and enhance studio container dev environment support 2026-06-04 21:52:38 +02:00
.yarnrc.yml feat: initialize studio apps and CLI workspace with supporting infrastructure and bookstore example 2026-05-25 12:10:02 +02:00
AGENTS.md chore: make Forgejo the source of authority, GitHub a read-only mirror 2026-11-10 19:34:42 +01:00
jest.config.ts feat: initialize studio apps and CLI workspace with supporting infrastructure and bookstore example 2026-05-25 12:10:02 +02:00
package.json feat: implement AuthBasic middleware and introduce HTTP utility package with status and method definitions 2026-06-08 15:00:50 +02:00
README.md docs: explain why container images target arm64 only 2026-11-10 21:30:54 +01:00
tsconfig.json refactor: update CoreUI and package ui* dependency references to CoreUX and ux* 2026-06-02 23:31:27 +02:00
yarn.lock feat(api-gateway): back redis cache with @quatrain/cache-redis adapter (#7) 2026-09-30 11:48:07 +02:00

Core Applications & Deployments (CoreApps)

Important

The source of authority is git.qtrn.io/quatrain/core-apps: issues, pull requests, wiki and CI live there. github.com/Quatrain/CoreApps is a read-only mirror.

This monorepo houses all visual dashboard environments, local modeling APIs, API routing proxies, and containerized deployments built on top of the Core framework (by Quatrain).


🏗️ Repository Architecture

This workspace is managed using Yarn Berry (v4) Workspaces and is organized as follows:

CoreApps/
├── apps/
│   ├── studio-api/      # Local modeling API server (Express/SQLite)
│   └── studio-web/      # Visual developer studio frontend (React/Mantine)
├── containers/
│   ├── api-gateway/     # Traefik & Redis routing gateway container
│   └── studio-image/    # Bundled Visual Environment image
├── examples/
│   └── bookstore/       # Bookstore reference sandbox application
└── bin/
    ├── publish_container.sh # Container build & push to qtrn.io (Forgejo Actions)
    └── push_tag.sh      # Automated release tagging script

🛠️ Local Development

Prerequisites

To link and resolve package dependencies locally, the Core repository MUST be cloned in a sibling directory:

CODE/QUATRAIN/
├── Core/            # Foundation library packages
└── CoreApps/        # Applications & deployments (this repository)

All package linkages (@quatrain/*) are automatically mapped from the Core sibling packages via portal: resolutions.

Setup and Installation

Install dependencies and link workspaces:

yarn install

Running the Workspaces

Start all development environments concurrently:

yarn dev

Compiling

Build all applications and container setups sequentially:

yarn build

🚀 Versioning & Deployment

Deployments and releases are automated via Forgejo Actions on git.qtrn.io; images are published to the sovereign registry qtrn.io/quatrain/*:

  • Release Tagging: Run the bin/push_tag.sh script to bump the monorepo version patch, create a Git tag, and push it to the remote.
  • API Gateway Image: .forgejo/workflows/publish-api-gateway.yaml runs bin/publish_container.sh api-gateway.
  • Studio Environment Image: .forgejo/workflows/publish-studio-image.yaml runs bin/publish_container.sh studio-image.
  • Pushes to develop publish :develop and :sha-<commit>; pushes to main bump the patch version, publish :<version> and :latest, and tag <container>-v<version>. Secrets REGISTRY_USER and REGISTRY_TOKEN are required.
  • Images are published for linux/arm64 only: ARM64 is more resource-efficient (better performance per watt and lower instance cost), which is why the qtrn.io nodes and runners all run on it. Builds are therefore native, without emulation. PLATFORMS can request other platforms, built under QEMU; bun install is known to crash under amd64 emulation.

⚖️ License

Licensed under the GNU Affero General Public License v3.0 (AGPL v3).