null/Queue-North-Website
null
/
Queue-North-Website
1
0
Fork 0
Code Issues 27 Pull Requests Packages Projects Releases Wiki Activity
Queue-North-Website/.env.example

33 lines
971 B
Plaintext
Raw Permalink Normal View History

feat: Docker batch 0.2.1 — production-ready containerization - Multi-stage Dockerfile with non-root nodejs user - Healthcheck using Node 20 built-in fetch (no wget) - docker-entrypoint.sh: root permission fix, then exec to nodejs - server/db.js: deferred SQLite init for Docker volume permissions - docker-compose.yml with named volumes for persistence - .dockerignore and .env.example added - README updated with Docker usage section Security reviewed by Private Hudson. All blockers resolved.
2026-05-12 01:57:55 -05:00
# Environment configuration
# Copy this file to .env and customize as needed
NODE_ENV=production
SERVER_PORT=3001
fix(zoho): fix OAuth token endpoint, improve lead field mapping, add upsert - Fix critical bug: token refresh now uses ZOHO_ACCOUNTS_DOMAIN (accounts.zoho.com) instead of API domain (www.zohoapis.com). The OAuth token endpoint lives on a different domain. - Remove unnecessary redirect_uri from refresh token request - Add ZOHO_ACCOUNTS_DOMAIN env var (separate from API domain) - Split contact name into First_Name/Last_Name for Zoho schema - Replace Service_Interest (non-standard field) with Description + Lead_Source: Website (standard picklist value) - Switch from Insert to Upsert API with duplicate_check_fields: [Email] so duplicate submissions update instead of error - Add trigger: ['workflow'] for explicit workflow control - Add token refresh retry (1 retry on transient failure) - Add ZOHO_CASES_ENABLED env var for future Cases forwarding - Update .env.example with full Zoho config documentation - Update FUTURE.md with detailed Phase 7 Zoho integration plan - Remove obsolete ZOHO_REDIRECT_URI from Dockerfile
2026-05-17 18:37:10 -05:00
# Zoho CRM Integration
feat(zoho): WebToLead forwarding mode, veteran-owned certified badge, Docker/env/CI updates (batch 0.9.1)
2026-06-14 16:08:29 -05:00
# Preferred current setup: webtolead for contact leads using the legacy Zoho form tokens.
ZOHO_FORWARDING_MODE=webtolead
ZOHO_WEBTOLEAD_ENABLED=false
ZOHO_WEBTOLEAD_URL=https://crm.zoho.com/crm/WebToLeadForm
ZOHO_WEBTOLEAD_XNQSJSDP=
ZOHO_WEBTOLEAD_XMIWTLD=
ZOHO_WEBTOLEAD_ACTION_TYPE=TGVhZHM=
ZOHO_WEBTOLEAD_RETURN_URL=null
ZOHO_WEBTOLEAD_ZC_GAD=
# Standby REST API/OAuth setup. Set ZOHO_FORWARDING_MODE=api and ZOHO_ENABLED=true to use it.
fix(zoho): fix OAuth token endpoint, improve lead field mapping, add upsert - Fix critical bug: token refresh now uses ZOHO_ACCOUNTS_DOMAIN (accounts.zoho.com) instead of API domain (www.zohoapis.com). The OAuth token endpoint lives on a different domain. - Remove unnecessary redirect_uri from refresh token request - Add ZOHO_ACCOUNTS_DOMAIN env var (separate from API domain) - Split contact name into First_Name/Last_Name for Zoho schema - Replace Service_Interest (non-standard field) with Description + Lead_Source: Website (standard picklist value) - Switch from Insert to Upsert API with duplicate_check_fields: [Email] so duplicate submissions update instead of error - Add trigger: ['workflow'] for explicit workflow control - Add token refresh retry (1 retry on transient failure) - Add ZOHO_CASES_ENABLED env var for future Cases forwarding - Update .env.example with full Zoho config documentation - Update FUTURE.md with detailed Phase 7 Zoho integration plan - Remove obsolete ZOHO_REDIRECT_URI from Dockerfile
2026-05-17 18:37:10 -05:00
ZOHO_ENABLED=false
ZOHO_API_DOMAIN=https://www.zohoapis.com
ZOHO_ACCOUNTS_DOMAIN=https://accounts.zoho.com
ZOHO_CLIENT_ID=
ZOHO_CLIENT_SECRET=
ZOHO_REFRESH_TOKEN=
ZOHO_CASES_ENABLED=false
RECAPTCHA
2026-05-25 20:20:15 -05:00
# Google reCAPTCHA
# Leave disabled until a real Google reCAPTCHA site key and secret key are configured.
RECAPTCHA_ENABLED=false
RECAPTCHA_SECRET_KEY=
RECAPTCHA_MIN_SCORE=0.5
VITE_RECAPTCHA_SITE_KEY=