Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Local hosted frontend keeps using api.eventyay.com despite API_HOST being defined #9195

Open
kennyboy55 opened this issue Mar 18, 2025 · 0 comments

Comments

@kennyboy55
Copy link

Describe the bug
I am trying to host the open-event-server and open-event-frontend locally on my home server. When accessing the frontend locally, I can see in the network traffic that it is using api.eventyay.com as the backend. However, I have the env var API_HOST set to the local address of the api.

Docker-compose config

version: "3"

services:
  opev-front:
    image: eventyay/open-event-frontend:master
    container_name: opev-front
    ports:
      - "4200:4000"
    restart: unless-stopped
    volumes:
      - ./front/images:/var/www/html/public/img
      - ./front/logs:/var/www/html/app/logs
      - ./front/backup:/var/www/html/public/backup
      - ./front/theme:/var/www/html/public/themes
      - ./front/migrate:/var/www/html/app/migrations
    env_file: .env
    environment:
      - API_HOST=opev-api
      - MAP_DISPLAY=embed
      - FASTBOOT_DISABLED=true
    depends_on:
      - opev-api
    logging:
      driver: 'json-file'
      options:
        max-size: '10m'
        max-file: '5'

  opev-database:
    image: postgis/postgis:12-3.0-alpine
    container_name: opev-database
    restart: unless-stopped
    volumes:
      - ./database:/var/lib/postgresql/data
    env_file: .env
    environment:
      - POSTGRES_USER
      - POSTGRES_PASSWORD
      - POSTGRES_DB
    logging:
      driver: 'json-file'
      options:
        max-size: '10m'
        max-file: '5'

  opev-redis:
    image: redis:3-alpine
    container_name: opev-redis
    restart: unless-stopped
    command: redis-server
    volumes:
      - ./redis:/var/lib/redis/data
    logging:
      driver: 'json-file'
      options:
        max-size: '10m'
        max-file: '5'

  opev-api:
    image: eventyay/open-event-server:master
    container_name: opev-api
    restart: unless-stopped
    env_file: .env
    depends_on:
      - opev-database
      - opev-redis
    volumes:
      - ./api/static:/data/app/static
      - ./api/generated:/data/app/generated
    logging:
      driver: 'json-file'
      options:
        max-size: '10m'
        max-file: '5'
    ports:
      - 8483:8080

  opev-celery:
    image: eventyay/open-event-server:master
    container_name: opev-celery
    depends_on:
      - opev-api
    env_file: .env
    environment:
      - C_FORCE_ROOT=true
    command: celery
    logging:
      driver: 'json-file'
      options:
        max-size: '10m'
        max-file: '5'

.env file

API_HOST=opev-api

POSTGRES_USER=opev
POSTGRES_PASSWORD=<redacted>
POSTGRES_DB=opev

POSTGRES_HOST=opev-database
REDIS_HOST=opev-redis

DATABASE_URL=postgresql://opev:<redacted>@opev-database:5432/opev
REDIS_URL=redis://opev-redis:6379/0

ADMIN_EMAIL=<redacted>
ADMIN_PASSWORD=<redacted>
      
INTEGRATE_SOCKETIO=false

APP_CONFIG=config.DevelopmentConfig
FLASK_APP=app.instance

SECRET_KEY=<redacted>

I can access the open-event-server locally by going to the 8483 port.

As a side note, the ADMIN_* keys which should create that user according to the examples, do nothing and only the default [email protected] is created.

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

No branches or pull requests

1 participant