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>
36 lines
1.6 KiB
Bash
36 lines
1.6 KiB
Bash
# ---------------------------------------------------------------------------
|
|
# Public (baked into the client bundle at build time — never put secrets here)
|
|
# ---------------------------------------------------------------------------
|
|
VITE_SITE_URL=https://fitness.exorecovery.ru
|
|
|
|
# Sub-path the site is served from, if any. Leave as "/" when it sits at the
|
|
# domain root; set to "/fitness/" if it is ever mounted under a sub-path.
|
|
VITE_BASE_PATH=/
|
|
|
|
# ---------------------------------------------------------------------------
|
|
# Server
|
|
# ---------------------------------------------------------------------------
|
|
# One port per landing so all four can run side by side:
|
|
# fitnes 3000, hotel 3001, medcenterphysio 3002, medcenterstart 3003.
|
|
PORT=3000
|
|
|
|
# ---------------------------------------------------------------------------
|
|
# amoCRM — server-side only, never exposed to the browser
|
|
# ---------------------------------------------------------------------------
|
|
# Your account subdomain: for https://exotherapy.amocrm.ru put "exotherapy"
|
|
AMO_SUBDOMAIN=
|
|
|
|
# Long-lived access token.
|
|
# amoCRM → Настройки → Интеграции → Создать интеграцию → Внешняя интеграция →
|
|
# open it → tab "Ключи и скопы" → «Генерировать токен» (долгосрочный, ~1 год).
|
|
AMO_LONG_LIVED_TOKEN=
|
|
|
|
# Pipeline (воронка) the leads land in. The lead is placed in its first stage.
|
|
AMO_PIPELINE_ID=10980758
|
|
|
|
# Optional: numeric id of the amoCRM user leads are assigned to.
|
|
AMO_RESPONSIBLE_USER_ID=
|
|
|
|
# Optional: comma-separated tags added to every lead.
|
|
AMO_LEAD_TAGS=fitness-landing
|