Yuriy PanovandClaude Opus 5
51f39c9b88
Bring deploy/ in line with the renamed app directories and with the domains that are actually configured in the per-app .env files: fitnes fitness.exorecovery.ru 3000 fitness-landing hotel hotel.exorecovery.ru 3001 hotel-landing medcenterphysio physio.exorecovery.ru 3002 physio-landing medcenterstart start.exorecovery.ru 3003 start-landing apps.conf, the README provisioning steps (directories, bare clones, systemd units, the sudoers whitelist) and the exo-deploy usage line all used the old medcenter / medcenterpersonal keys. The README table and app.build.env.example still carried the *_DOMAIN placeholders. Also refresh the tracked .env.example files: real VITE_SITE_URL values instead of the old exodevices.ru sub-paths, and the amo lead tags that match apps.conf. Two lockfile fixes, both of which broke `npm ci` in exo-deploy: - medcenterstart had no lockfile at all after package-lock.json and pnpm-lock.yaml were removed — restore package-lock.json and keep the pnpm one deleted, since the deploy path is npm; - medcenterphysio/package-lock.json had lost "resolved" and "integrity" on 147 of its 236 entries — restore the complete file. Verified: exo-render-nginx renders all four vhosts with no leftover placeholders, and every package-lock.json agrees with its package.json. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
27 lines
908 B
Bash
27 lines
908 B
Bash
# Install as /etc/exo/<app>.env — chown root:exo, chmod 640
|
|
# Runtime config for the Node process. systemd injects this via EnvironmentFile.
|
|
# CONTAINS A SECRET: never commit a filled-in copy.
|
|
|
|
NODE_ENV=production
|
|
HOST=127.0.0.1
|
|
# Per deploy/apps.conf: fitnes 3000, hotel 3001, medcenterphysio 3002, medcenterstart 3003
|
|
PORT=3000
|
|
|
|
# amoCRM account subdomain. "exotherapy", "exotherapy.amocrm.ru" and a full URL
|
|
# are all accepted (server/src/config.ts).
|
|
AMO_SUBDOMAIN=zvvamoexotherapyru
|
|
|
|
# Long-lived token, valid ~1 year. Paste out of band; rotate before it expires
|
|
# (its failure mode is a 401 surfaced to visitors as a 502).
|
|
AMO_LONG_LIVED_TOKEN=
|
|
|
|
AMO_PIPELINE_ID=10980758
|
|
AMO_RESPONSIBLE_USER_ID=
|
|
|
|
# Per-landing tag, per deploy/apps.conf.
|
|
AMO_LEAD_TAGS=fitness-landing
|
|
|
|
# Optional, undocumented in the app .env.example files: overrides the amoCRM
|
|
# domain (default amocrm.ru).
|
|
# AMO_DOMAIN=amocrm.ru
|