Yes so that guide should make it clearer that you need to stop your existing Baserow server to then launch a version which only starts and exposes the database when using the baserow/baserow
image and the start-only-db
command.
If you instead want to launch both the embedded postgres database, access it remotely and have Baserow running at the same time then I recommend you launch and run your own postgres database separately from Baserow and configure Baserow to use that postgres database. Then you can expose your postgres database as you see fit in a safe manner.
For example you could do this by using docker-compose
with the following file:
version: "3.4"
services:
baserow:
container_name: baserow
image: baserow/baserow:1.10.2
environment:
BASEROW_PUBLIC_URL: 'http://localhost'
DATABASE_HOST: "db"
DATABASE_PASSWORD: REPLACE_ME_WITH_YOUR_PASSWORD
ports:
- "80:80"
volumes:
- baserow_data:/baserow/data
db:
image: postgres:11
restart: unless-stopped
ports:
- "5432:5432"
depends_on:
- baserow
environment:
POSTGRES_USER: baserow
POSTGRES_PASSWORD: REPLACE_ME_WITH_YOUR_PASSWORD
POSTGRES_DB: baserow
volumes:
- pg_data:/var/lib/postgresql/data
volumes:
baserow_data:
pg_data:
Do you have existing data in your current Baserow server you would need to transfer to this new database?