Skip to content

chore(ops): turn on the legacy highlight rewrite in the PM2 config - #80

Merged
HMarzban merged 1 commit into
mainfrom
chore/hocus-rewrite-legacy-highlights
Nov 15, 2026
Merged

HMarzban merged 1 commit into
mainfrom
chore/hocus-rewrite-legacy-highlights

Conversation

@HMarzban

Copy link
Copy Markdown
Contributor

What

Sets HOCUS_REWRITE_LEGACY_HIGHLIGHTS: "1" in the editor-hocus env of ecosystem.config.cjs.

Why

Production has run Hocus with the flag since 2026-11-15. It was set with pm2 restart --update-env and pm2 save, so it lives only in PM2's dump. pm2 start ecosystem.config.cjs or pm2 reload ecosystem.config.cjs would drop it. Release N tabs are gone (client_schema shows only current builds with refused:0), so the rewrite is safe to keep on permanently.

Deploy

No action: the running process already has the flag. The next git pull brings the file in line with it.

Checks

  • The config loads, and editor-hocus gets the flag (bun -e require check).
  • Biome is clean.
  • tests/unit/ci passes.

Production has run editor-hocus with HOCUS_REWRITE_LEGACY_HIGHLIGHTS=1
since 2026-11-15, set with pm2 restart --update-env and pm2 save. Put it
in ecosystem.config.cjs so pm2 start or reload from the file keeps it.
@HMarzban
HMarzban merged commit 8930b0c into main Nov 15, 2026
2 checks passed
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.

1 participant