LaneAward Infrastructure Reference

Environment Topology Map

Graphic reference for the current LaneAward development workflow across the local Mac, the live AWS staging runtime, and the AWS-hosted public landing environment.

Current live topology verified on 2026-04-13 AWS staging runtime is active

Current Live Workflow

Development starts on the Mac, publishes into the dedicated AWS staging runtime, and promotes outward to the separate AWS public landing page.
Current state

Local Mac

Primary development workstation
/Users/donaldscott/Project-Code/laneaward/repo
/Users/donaldscott/Project-Code/laneaward/repo_prod
workforce_app/data/workforce.db
Source of code edits, HTML docs, and the local SQLite refresh workflow.
Deploy to staging
→

AWS Staging Runtime

Official public staging host
Host: staging.laneaward.com
SSH: ssh -i ~/.ssh/lane_webserver.pem ubuntu@3.130.69.109
Web root: /var/www/laneaward-staging
DB: /var/lib/laneaward-staging/workforce.db
Service: laneaward-workforce-api-staging.service
Public landing
→

AWS Production

Public landing-page host
Host: ai.laneaward.com
SSH: ssh -i ~/.ssh/lane_webserver.pem ubuntu@3.130.69.109
Web root: /var/www/html
Role: production landing page

Mac to AWS Staging

  • ssh -i ~/.ssh/lane_webserver.pem ubuntu@3.130.69.109
  • Staging web root: /var/www/laneaward-staging
  • Staging DB: /var/lib/laneaward-staging/workforce.db
  • Staging service: laneaward-workforce-api-staging.service

AWS Staging URLs

  • Time On Tasks: https://staging.timeontasks.laneaward.com/
  • Operations Console: https://staging.console.laneaward.com/
  • API health: https://staging.timeontasks.laneaward.com/api/health
  • Legacy host: https://staging.laneaward.com/ (backward compat)
  • API port on host: 127.0.0.1:9193

AWS Production Today

  • ssh -i ~/.ssh/lane_webserver.pem ubuntu@3.130.69.109
  • Live root: /var/www/html
  • Public landing: https://ai.laneaward.com/
  • Elastic IP: 3.130.69.109

AWS Runtime Split

The current AWS layout keeps staging and production on the same instance while isolating them by host header, web root, service, and SQLite database.
Current target

Local Mac

Development origin for both staging and production deploys
ssh -i ~/.ssh/lane_webserver.pem ubuntu@3.130.69.109
SSH / rsync deploys
→

AWS Ubuntu Server at 3.130.69.109

Same Elastic IP, separate host headers, separate runtime surfaces

Current AWS Staging

Hosts: staging.timeontasks.laneaward.com · staging.console.laneaward.com
Time On Tasks: staging.timeontasks.laneaward.com → /var/www/laneaward-staging
Console: staging.console.laneaward.com → /var/www/laneaward-staging-console
Legacy: staging.laneaward.com (backward compat)
Live DB: /var/lib/laneaward-staging/workforce.db
Live service: laneaward-workforce-api-staging.service
API port: 9193
TLS cert: /etc/letsencrypt/live/staging.timeontasks.laneaward.com/ (SAN)
Purpose: stable public staging for app validation, reliability testing, and pre-production database checks.
Status: live and ready for reliability testing. PWA install verified 2026-04-13.

Current AWS Production

Host: ai.laneaward.com
Nginx server_name: ai.laneaward.com
Live web root: /var/www/html
Current role: production landing page
TLS path: /etc/letsencrypt/live/ai.laneaward.com/
Purpose: public entry point for app discovery, PIN gate, and final production links.
Same server, separate host headers and runtimes
staging.timeontasks.laneaward.com → 3.130.69.109
staging.console.laneaward.com → 3.130.69.109
staging.laneaward.com → 3.130.69.109
timeontasks.laneaward.com → 3.130.69.109
console.laneaward.com → 3.130.69.109
ai.laneaward.com → 3.130.69.109

Current AWS Staging Isolation

  • Separate Nginx site for staging.laneaward.com
  • Separate web root: /var/www/laneaward-staging
  • Separate SQLite DB: /var/lib/laneaward-staging/workforce.db
  • Separate backend service: laneaward-workforce-api-staging.service

Why This Split Helps

  • Creates one authoritative public staging path that is much closer to production
  • Keeps public production and public staging from sharing the same runtime data
  • Makes AWS the authoritative network path before production app cutover
  • Removes the need to validate over a weaker home-network path

Current Truth Notes

  • staging.timeontasks.laneaward.com and staging.console.laneaward.com are the canonical staging URLs as of 2026-04-13
  • All 6 subdomains resolve to the same AWS Elastic IP (3.130.69.109) via a single SAN TLS certificate
  • staging.laneaward.com remains active as a backward-compatible alias
  • timeontasks.laneaward.com and console.laneaward.com show Coming Soon placeholders pending production cutover
  • ai.laneaward.com is live from AWS at /var/www/html (Launchpad)
  • PWA install verified 2026-04-13 on Chromebook, iPad Pro 13", Android tablet (10"), and Mac workstation

Terminal Connection Matrix

Quick reference for the direct terminal entry points associated with the topology above.

AWS Server

  • ssh -i ~/.ssh/lane_webserver.pem ubuntu@3.130.69.109
  • Current live public host: ai.laneaward.com
  • Current live staging host: staging.laneaward.com

Public and Staging Domains

  • AWS production landing: ai.laneaward.com
  • AWS staging Time On Tasks: staging.timeontasks.laneaward.com
  • AWS staging Console: staging.console.laneaward.com
  • Legacy staging host: staging.laneaward.com (backward compat)
  • Production placeholders: timeontasks.laneaward.com, console.laneaward.com

Verified from local project documentation, local SSH configuration, and DNS checks completed on 2026-04-13. The topology above reflects the official current workflow and hosted runtime split.