Local Backend via Docker

VS Code extension that provides a guided UI for running the backend local setup flow (dev-start.sh) for apm0013625-backend-services.

Screenshot

What this extension does

• Opens a setup webview via command: Start Local Backend Docker
• Runs the backend setup script from VS Code with prefilled environment values
• Supports both workspace modes:
  • Open parent folder/workspace that contains apm0013625-backend-services
  • Open apm0013625-backend-services repo directly
• Prefills Customer from src/local-configuration/configuration.json (defaultCustomer)
• Exposes setup controls:
  • Customer
  • Environment (test2, test3, stage)
  • Clone or Update Repositories
  • Optional repo-update inputs: passphrase, branch, update RN
  • Build with --no-cache
  • Local App Config toggle
  • Local Sanity toggle
• Updates configuration.json toggles (localConfig / localSanity) for services (excluding gateway)
• Sends setup values to dev-start.sh using task environment variables
• Includes quick actions:
  • Refresh App Config (set-app-config.sh)
  • Refresh Redis (flushes Redis container)

Usage

1. Open Command Palette (Cmd+Shift+P)
2. Run Start Local Backend Docker
3. Fill in the form and click Start Setup
4. Monitor progress in the shared task terminal: Local Backend Docker Setup

Workspace expectations

The extension searches for apm0013625-backend-services automatically.

• If your workspace root is apm0013625-backend-services, it uses that directly.
• If your workspace root is a parent folder, it looks for apm0013625-backend-services inside it.

If the repo is not found, the webview shows an error telling you to open either the backend repo directly or its parent workspace.

Requirements

• VS Code >=1.70.0
• Bash
• Docker / Docker Compose
• Node.js
• All prerequisites needed by apm0013625-backend-services/src/scripts/dev-start.sh

Command

• localBackendDocker.start → Start Local Backend Docker

Development

1. npm install
2. npm run compile
3. Press F5 to launch an Extension Development Host

Packaging / Publishing

• Package: vsce package
• Publish: vsce publish

If publishing times out (ETIMEDOUT), verify proxy/network settings and retry from a network path that allows Visual Studio Marketplace egress.