Platform operations

System overview

Live application, release, and recovery state for the JewelLink SR250.

Applications healthy—active release listeners
Current release—latest activated revision
Cloud-source reads—Loading administrative policy
Recovery targetD:post-success system image

Application fleet

Active and rollback slots remain independently available.

Release timeline

Immutable Gitea-backed releases

Sign in for release history.

Recent command jobs

Audited operator activity

Sign in for command history.

Runtime control

Applications

Health, active/rollback slots, releases, databases, and guarded restarts.

Revision promotion

Deployments

Upload to a subordinate Gitea branch, validate, and promote without overwriting the active release.

Auto-merge always defaults off.Every upload creates an isolated branch. Promotion requires validation, immutable build output, candidate health gates, and an atomic cutover.
No deployment activity has been recorded yet.

Source authority

Gitea workflow

Local mirrors, server-test branches, revisions, and promotion gates.

CR

Count Retail

MatthewBulthuis/countretail

server-test
JL

JewelLink

MatthewBulthuis/jewellink-app

server-test
MP

Mapper

MatthewBulthuis/edt-middleware

server-test

Promotion pipeline

  1. UploadCreate subordinate branch
  2. ValidateBuild and dependency gates
  3. CandidateStart inactive release and database
  4. VerifyAuth and protected workflow probes
  5. PromoteAtomic NGINX cutover
  6. RetainKeep immediate rollback release

Traffic control

NGINX

Validate configuration before every graceful reload; active upstreams always retain a healthy backup.

Active upstream map

Generated from the protected blue/green control file

Authentication required

Continuity

Refresh & recovery

Shadow refreshes never modify live cloud systems and only promote after all gates pass.

Midnight refresh

Scheduled task evidence from this SR250

Loading
12:00 AM Central
Status is being collected.
  • Mirror approved upstream into local Gitea
  • Build an immutable inactive release
  • Restore data into shadow databases
  • Verify health, auth, and protected workflows
  • Cut over NGINX atomically
  • Retain the previous release for rollback

Windows recovery image

Post-success task evidence from this SR250

Loading
D:
Status is being collected.

Created only after the deployment reaches a verified terminal success. Oldest recovery images are removed only when storage pressure requires it.

Accountability

Jobs & audit

Every sign-in, command, result, deployment, and recovery action is recorded.

Command jobs

Sign in to view jobs.

Audit events

Sign in to view audit events.

Access control

Users

Create and manage owner, administrator, operator, and read-only access.

Server Machine is permanent.The local-console owner is undeletable. Every user change is audited; all remote accounts require HTTPS, a password, and an authenticator code.
Sign in as an administrator to manage users.