fix(consumer): Use relative API URLs for findadispo/findagram

The consumer frontends were hardcoded to use cannaiq.co as the API
URL, but each domain has its own /api path in the ingress that routes
to the shared backend. Using relative URLs allows each site to make
API calls to its own domain.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
Kelly
2025-12-09 13:38:10 -07:00
parent 7e517b5801
commit 7fe7d17b43
2 changed files with 6 additions and 6 deletions

View File

@@ -12,9 +12,9 @@ RUN npm install
# Copy source files
COPY . .
# Set build-time environment variable for API URL (CRA uses REACT_APP_ prefix)
# All consumer sites use cannaiq.co/api as the backend
ENV REACT_APP_API_URL=https://cannaiq.co
# Note: REACT_APP_API_URL is intentionally NOT set here
# The frontend uses relative URLs (same domain) in production
# API calls go to /api/* which the ingress routes to the backend
# Build the app (CRA produces /build, not /dist)
RUN npm run build

View File

@@ -12,9 +12,9 @@ RUN npm install
# Copy source files
COPY . .
# Set build-time environment variable for API URL (CRA uses REACT_APP_ prefix)
# All consumer sites use cannaiq.co/api as the backend
ENV REACT_APP_API_URL=https://cannaiq.co
# Note: REACT_APP_API_URL is intentionally NOT set here
# The frontend uses relative URLs (same domain) in production
# API calls go to /api/* which the ingress routes to the backend
# Build the app (CRA produces /build, not /dist)
RUN npm run build