BifrOSt-Web

public

Latest change 45b4f25c107d9fc535a9d87bfb2c24aa5f1eda14 - Deploy BifrOSt Web through AkurAI Build by Ólafur Búi Ólafsson

# BifrOSt Web Agent Guide

## Scope

This repository owns the BifrOSt website. Keep operating-system, installer, release-signing, and application source in the sibling BifrOSt repositories.

## Titan-only execution

- A laptop is a source-control client only. Do not compile, test, bundle, serve, or run asset pipelines on it.
- Commit only intended source changes, push them to the hosted Git remote, then fast-forward Titan's checkout with `git pull --ff-only`.
- Run all formatting, checks, tests, builds, previews, and deployment work on Titan.
- Never use file synchronization as a substitute for Git. Titan must execute the exact pushed commit.
- Do not add GitHub Actions or another workload path that bypasses Titan.

## AkurAI Build deployment

- `.akurai.yml` is the only CI/CD workflow. Its native jobs run on Titan as `olibuijr`; paths must use `/home/olibuijr`.
- Production promotion is approval-protected. The deploy job atomically installs the exact pipeline bundle and restarts `bifrost-web.service`.
- The application listens on Titan's VPN-reachable port `8092`; the EC2 nginx edge publishes it as `https://bifrost.olibuijr.com`.
- Never place credentials, private keys, or DNS/TLS secrets in this repository or pipeline arguments.

## Verification

Run the narrowest check for the changed contract on Titan. For UI changes, launch the Titan-built site and exercise the affected path in a browser; compilation alone is not verification.

## Repository hygiene

Do not commit generated build output, caches, credentials, or deployment secrets. Treat unexpected working-tree changes as user work and do not overwrite them.