Error generating BASEROW_PUBLIC_URL in docker-compose

Technical Help
,
1

Hi guys all good? I noticed an error in docker-compose that I am generating from Base.

When I use generate baserow without the directive BASEROW_CADDY_ADDRESSES it only installs as http://localhost:8000 and does not accept the directive that I put in BASEROW_PUBLIC_URL:

For the Baserow installation to use the domain I need to use the BASEROW_CADDY_ADDRESSES and so it reads the correct domain.

 environment:
   DB_HOST: db
   DB_NAME: baserow
   DB_USER: baserow
   DB_PASSWORD: ${POSTGRES_PASSWORD}
   USE_X_FORWARDED_HOST: "true"
   BASEROW_PUBLIC_URL: https://anyvalue.com
   EMAIL_BACKEND

Is there something I’m doing wrong?

2

Hi @rafaelrodrigues can you provide the full docker-compose file you are trying to use and all docker / docker-compose commands you use to launch said files?

Do you want to have automatic HTTPS from our embedded Caddy? If not then you don’t want to set BASEROW_CADDY_ADDRESSES at all.

3

Yes of course.

version: '3'
services:
  baserow:
    image: baserow/baserow:latest
    container_name: baserow
    environment:
      - DB_ENGINE=django.db.backends.postgresql
      - DB_NAME=baserow
      - DB_USER=baserow
      - DB_PASSWORD=baserow
      - DB_HOST=postgres
      - DB_PORT=5432
      - DEBUG=false
      - SECRET_KEY=p4%j#wx%qxzn!^&#6dn4p#i9+=dp-j!m-7qmx^rmj^%c+l_=4z
      - BASEROW_PUBLIC_URL:=https://base.example.com
      - EMAIL_BACKEND=django.core.mail.backends.console.EmailBackend
    depends_on:
      - postgres
    restart: always
    volumes:
      - baserow_data:/baserow/data

and when I go to see the log appears .

WARNING: Baserow is configured to use a BASEROW_PUBLIC_URL of http://localhost. If you attempt to access Baserow on any other hostname requests to the backend will fail as they will be from an unknown host. Please set BASEROW_PUBLIC_URL if you will be accessing Baserow from any other URL then http://localhost.
4

How come you have BASEROW_PUBLIC_URL: with a :? Can you remove this and try again? Also you will want to change that secret_key value you’ve now shared publically FYI