03-Feb-2026 — Secrets, Paths and 4 more areas: 6 features and 1 fix #146

build 459commit c19b47d


Add loadSecretsWithFallback and loadSecretsForEnvironmentFromDatabase to support reading secrets from the database ENVIRONMENTS config when running on deployed servers. Falls back to file-based secrets for local development. Secrets are built from:

cli: add GitHub secrets sync command for environment management (#146)

Add ngx-cli github command with reconcile, sync, and push subcommands to manage the CONFIGS_JSON GitHub secret from the database source of truth. This enables regular syncing when environments are created or modified.

backup: global AWS credentials, S3 path improvements, and DRY refactoring (#146)

User Guide

Global Backup Configuration

You can now configure global AWS credentials in the Settings tab under 'Global AWS S3 Configuration'. This allows a single set of credentials to manage backups across all environments, with per-environment settings used as fallback. New Settings Fields:

Backup Improvements

Environment Configuration

Technical Changes

S3 Path Construction

DRY Refactoring

Credential Resolution

Code Quality

environment-setup: comprehensive environment management overhaul with API and MongoDB migration (#146)

Introduces new environment configuration API, MongoDB cluster-based config, and enhanced UI with vendor branding and dashboard links. New Environment Configuration API:

environment-setup: add automated environment creation and CLI enhancements (#146)

New Features for Users: Environment Setup (Web UI) The new Environment Setup page (Admin > Environment Setup) allows administrators to create complete NGX-Ramblers environments for new Ramblers walking groups through a guided wizard:

  1. Enter your Ramblers API key and select your walking group
  2. Configure external services (MongoDB, AWS, Brevo email, maps)
  3. Set up an admin user account
  4. Deploy to fly.io with one click The wizard handles all infrastructure provisioning automatically including:

Technical Changes: CLI Implementation:

release-notes: add technical article publishing script

paths: use resolveClientPath for non-vcs file access (#146)

Fix path resolution for secrets and configs.json files when running in production mode where code executes from ts-gen directory.