Skip to content

Add dev2 deploy automation - #237

Open
aditya-damerla128 wants to merge 2 commits into
devfrom
fix/issue-234-dev2-deploy
Open

Add dev2 deploy automation#237
aditya-damerla128 wants to merge 2 commits into
devfrom
fix/issue-234-dev2-deploy

Conversation

@aditya-damerla128

@aditya-damerla128 aditya-damerla128 commented Jul 20, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • reuse the existing refserver and landing deploy workflows for dev pushes
  • add dev2 deploy jobs for both refserver and landing using direct SSH/rsync
  • preserve dev2's current /home/adamerla/ozwellai-api + PM2 + local .env shape while deploying build artifacts
  • make the landing manager URL environment-driven so dev2 can use ozwellconsole without dirty tracked files
  • include root workspace manifests in the refserver deploy package so remote installs can use the root lockfile

Validation

  • git diff --check
  • bash -n scripts/build-deploy-package.sh scripts/build-demo-package.sh
  • node --check landing-page/server.js
  • workflow YAML parse

Fixes #234

@aditya-damerla128 aditya-damerla128 linked an issue Jul 21, 2026 that may be closed by this pull request
@aditya-damerla128
aditya-damerla128 force-pushed the fix/issue-234-dev2-deploy branch from 1a8fd0a to f4979ed Compare July 27, 2026 16:07
@aditya-damerla128
aditya-damerla128 marked this pull request as ready for review July 27, 2026 19:57

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR extends the existing production deploy automation to also deploy on dev branch pushes (targeting the dev2 environment), and makes the landing page “Ozwell Manager” URL configurable via environment variables to avoid environment-specific tracked-file changes.

Changes:

  • Add dev branch triggers and branch-scoped concurrency for the reference-server and demo-site deploy workflows, and split deploy jobs into deploy-prod vs deploy-dev.
  • Implement dev2 deploy steps using direct SSH + rsync, preserving dev2’s /home/adamerla/ozwellai-api + PM2 + local .env shape.
  • Make the landing page manager URL environment-driven by injecting MANAGER_URL into HTML at serve time and using it for legacy redirects.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.

File Description
landing-page/server.js Adds MANAGER_URL env support and injects it into served HTML; uses it for /register.html redirect.
landing-page/public/landing.html Replaces hardcoded manager links with an injected __MANAGER_URL__ placeholder.
.github/workflows/deploy-reference-server.yml Adds dev branch deploy (dev2) and branch-scoped concurrency; gates prod deploy to main.
.github/workflows/deploy-demo.yml Adds workflow_dispatch, dev branch deploy (dev2), and branch-scoped concurrency; gates prod deploy to main.

Comment thread .github/workflows/deploy-reference-server.yml Outdated
Comment thread .github/workflows/deploy-demo.yml Outdated
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Workflows to automate dev deployment

2 participants