feat(deploy): add CROMERO dapp Phoenix deploy target #12

nsatoshi · 2026-04-25T22:56:00Z

nsatoshi commented

2026-04-25 22:56:00 +00:00

Summary

Wires the new d-bis/CROMERO dapp (Vite + thirdweb v5, two-chain asset transfer flow) into the existing Phoenix Deploy API pipeline so pushes to main on that repo land at https://d-bis.org/ecosystem/cromero/.

Companion to d-bis/CROMERO#1.

Changes

phoenix-deploy-api/deploy-targets.json — register d-bis/CROMERO :: default running scripts/deployment/phoenix-deploy-cromero-from-workspace.sh, with a healthcheck against the public URL.
scripts/deployment/phoenix-deploy-cromero-from-workspace.sh — build the staged workspace (npm ci && npm run build) and rsync dist/ to the NPMplus host (${IP_NPMPLUS:-192.168.11.167}) /var/www/ecosystem/cromero/. Best-effort nginx reload (host nginx + npmplus container). --dry-run supported. Build env (VITE_THIRDWEB_CLIENT_ID, VITE_PROJECT_WALLET_ADDRESS, etc.) is read from the Phoenix host environment (set via repo Actions secrets/vars on the CROMERO repo).
docs/03-deployment/CROMERO_DAPP_DEPLOYMENT.md — pipeline overview, the one-time nginx location block that must be installed on the NPMplus host, the required Actions secrets/vars, manual-trigger and dry-run recipes.

Required nginx location block (one-time, install on NPMplus host)

location /ecosystem/cromero/ {
    alias /var/www/ecosystem/cromero/;
    try_files $uri $uri/ /ecosystem/cromero/index.html;
}

This script does not modify nginx config — it only lands static files. Install the block once via NPMplus advanced-config (or directly in the d-bis.org server block), then redeploys are static-only.

Verification

python3 -c "import json; json.load(open(...deploy-targets.json))" parses (15 targets, was 14).
bash -n scripts/deployment/phoenix-deploy-cromero-from-workspace.sh clean.
Dry-run path is supported via --dry-run / DRY_RUN=1.

## Summary Wires the new [d-bis/CROMERO](https://gitea.d-bis.org/d-bis/CROMERO) dapp (Vite + thirdweb v5, two-chain asset transfer flow) into the existing Phoenix Deploy API pipeline so pushes to `main` on that repo land at `https://d-bis.org/ecosystem/cromero/`. Companion to [`d-bis/CROMERO#1`](https://gitea.d-bis.org/d-bis/CROMERO/pulls/1). ## Changes - `phoenix-deploy-api/deploy-targets.json` — register `d-bis/CROMERO :: default` running `scripts/deployment/phoenix-deploy-cromero-from-workspace.sh`, with a healthcheck against the public URL. - `scripts/deployment/phoenix-deploy-cromero-from-workspace.sh` — build the staged workspace (`npm ci && npm run build`) and rsync `dist/` to the NPMplus host (`${IP_NPMPLUS:-192.168.11.167}`) `/var/www/ecosystem/cromero/`. Best-effort nginx reload (host nginx + npmplus container). `--dry-run` supported. Build env (`VITE_THIRDWEB_CLIENT_ID`, `VITE_PROJECT_WALLET_ADDRESS`, etc.) is read from the Phoenix host environment (set via repo Actions secrets/vars on the CROMERO repo). - `docs/03-deployment/CROMERO_DAPP_DEPLOYMENT.md` — pipeline overview, the **one-time nginx location block** that must be installed on the NPMplus host, the required Actions secrets/vars, manual-trigger and dry-run recipes. ## Required nginx location block (one-time, install on NPMplus host) ```nginx location /ecosystem/cromero/ { alias /var/www/ecosystem/cromero/; try_files $uri $uri/ /ecosystem/cromero/index.html; } ``` This script does **not** modify nginx config — it only lands static files. Install the block once via NPMplus advanced-config (or directly in the d-bis.org server block), then redeploys are static-only. ## Verification - `python3 -c "import json; json.load(open(...deploy-targets.json))"` parses (15 targets, was 14). - `bash -n scripts/deployment/phoenix-deploy-cromero-from-workspace.sh` clean. - Dry-run path is supported via `--dry-run` / `DRY_RUN=1`.

nsatoshi added 1 commit 2026-04-25 22:56:01 +00:00

feat(deploy): add CROMERO dapp Phoenix target

AI Code Review / claude-review (pull_request) Failing after 2m41s

Details

Validate (PR) / run-all-validation (pull_request) Failing after 29s

Details

5a172101a6

Wire the new d-bis/CROMERO dapp (Vite + thirdweb v5, two-chain asset
transfer flow at https://d-bis.org/ecosystem/cromero/) into the
existing Phoenix Deploy API pipeline.

- phoenix-deploy-api/deploy-targets.json: register
  d-bis/CROMERO :: default running
  scripts/deployment/phoenix-deploy-cromero-from-workspace.sh, with a
  healthcheck against the public URL.
- scripts/deployment/phoenix-deploy-cromero-from-workspace.sh: build
  the staged workspace and rsync dist/ to the NPMplus host's
  /var/www/ecosystem/cromero/. Best-effort nginx reload; --dry-run
  supported. Defaults sourced from config/ip-addresses.conf.
- docs/03-deployment/CROMERO_DAPP_DEPLOYMENT.md: pipeline overview,
  one-time nginx location block, required Actions secrets/vars,
  manual-trigger and dry-run recipes.

Co-Authored-By: Nakamoto, S <defi@defi-oracle.io>

gitea-actionsbot commented

2026-04-25 22:57:47 +00:00

Claude encountered an error —— View job

I'll analyze this and get back to you.

**Claude encountered an error** —— [View job](http://127.0.0.1:3000/d-bis/proxmox/actions/runs/160) --- I'll analyze this and get back to you.

nsatoshi merged commit 525f992854 into master

2026-04-26 00:11:50 +00:00

nsatoshi referenced this issue from a commit

2026-04-26 00:11:52 +00:00

feat(deploy): add CROMERO dapp Phoenix deploy target (#12)

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: d-bis/proxmox#12