How to stop sample template file download during Docker install?

Technical Help
, ,
1

Problem

It seems installing Baserow using standalone Docker image installs hundreds of sample user files by default – and corresponding thumbnail and cover files for these original user files.

Question

Is there any environment variable that will prevent this from occurring while deploying a container?

Reason/my person use case

I am trying to synchronize all user_files between my remote server and my local mac using a server synchronization tool and having all these sample files in there is annoying.

2

Is this what you need?

https://baserow.io/docs/installation%2Finstall-with-docker-compose#disable-automatic-template-syncing

image
image709×181 23.9 KB

3

Thank you @Peter. I think this only works for Docker Compose though, right?

I just rebuilt my standalone docker image and passed this as an environment variable and all files were downloaded again!

4

Hey @bfranklin , can you give more detail on what your standalone docker image is/your Dockerfile and the command you are using to launch Baserow?

This environment variable will work on our official backend, all-in-one docker image and docker-compose setups. Heres an example of how to set it with the all-in-one docker image which works for me:

docker run \
  -d \
  --name baserow \
  -e BASEROW_PUBLIC_URL=http://localhost \
  -v baserow_data:/baserow/data \
  -p 80:80 \
  -p 443:443 \
  -e SYNC_TEMPLATES_ON_STARTUP=false \
  --restart unless-stopped \
  baserow/baserow:1.10.0
6

Thanks @nigel for those updated Docker commands (and @Peter). I finally realized I can just deploy the standalone Docker image using Docker Compose and probably have more control that way than using the command line. I also did this using Portainer where you store your Docker compose files as a “stack”

My container has the following customizations:
✓ Custom standard port of 3001
✓ Custom ssl port of 444 (should note that I opened this port in my firewall in advance … though Docker compose, I think, attempts to do this itself)
✓ Custom postgres port of 5432 (instead of default 5430)
✓ Stop synchronization/download of template files
✓ Custom domain with A record pointed to IP of server to allow for custom domain
✓ Postgres outside Docker image on local: This also just references a Postgres server outside the docker container but still hosted on the same server (localhost) by just pointing the DATABASE_HOST variable to the local IP (though the documentation has some other way of doing this that might be better?)

And this is the Docker compose used:

version: "3.4"
services:
  baserow:
    container_name: baserow
    image: baserow/baserow:1.10.0
    ports:
      - "3001:80"
      - "444:443"
    environment:
      BASEROW_PUBLIC_URL: http://baserow.mydomain.com:3001
      WEB_FRONTEND_SSL_PORT: 444
      WEB_FRONTEND_PORT: 3001
      DATABASE_HOST: 123.456.789.999
      DATABASE_PORT: 5432
      DATABASE_NAME: baserow
      DATABASE_USER: baserow
      DATABASE_PASSWORD: kjhakjhakjhak
      SYNC_TEMPLATES_ON_STARTUP: stop
    volumes:
      - data:/baserow/data
volumes:
  data:

I’d love to be able to actually add proper SSL and eliminate the need to have the custom ports in the domain but my attempts to get “BASEROW_CADDY_ADDRESSES” to work seem to be failing when I add it to this compose, add “https” and remove the “:3001” from the domain. I will, however, create a new post for this final issue I am running into since it’s separate.