Skip to main content

Baserow

Baserow{target=_blank} is used to create your own online database without technical experience. Our user friendly no-code tool gives you the powers of a developer without leaving your browser

AlternativeTo

Cloud-Hosted

Selfhosted

Installation

Administration

Usage

Migrate from one Instance to another

Migrating and backing up data is sparsely documented in baserow currently.

  1. Export data - this includes database and file storage

    • For docker all-in-one:

      docker-compose exec -it baserow ./baserow.sh backend-cmd manage export_workspace_applications {{old_workspace_id}} --indent

    • For selfhosted kubernetes exec into wsgi pod:

      cd /baserow/backend

      source ../venv/bin/activate

      ./baserow export_workspace_applications {{old_workspace_id}} --indent

  2. Move data to new instance. Depending on your setup via docker cp or kubectl cp

  3. Import data

    • For docker all-in-one:

      docker-compose exec -it baserow ./baserow.sh backend-cmd manage import_workspace_applications {{new_workspace_id}} {{filename exluding .zip or .json}}

    • For selfhosted kubernetes exec into wsgi pod:

      cd /baserow/backend

      source ../venv/bin/activate

      ./baserow import_workspace_applications {{new_workspace_id}} {{filename exluding .zip or .json}}

Note If you are working with self-hosted environment, there is only one workspace. So you need to insert one of the available workspace IDs.

Metadata

Kubernetes Metadata
  • Image: baserow/backend:2.1.6@sha256:ee7d288535842efe9e44874e8546d61f8e5e39be5ce2f22e8d4021489de6a71e
  • Image: minio/minio:RELEASE.2024-06-26T01-06-18Z@sha256:337d6f0e90b1992759b832ede340a170cc8ca5cd5db097898b15a3ed121351f7
  • Image: baserow/web-frontend:2.1.6@sha256:faad09cad54317fc6b4e5b8d77c921bc9f2536df24ff75dce5c4d3a29a693bf7
  • Image: valkey/valkey:9.0.3-alpine@sha256:e1095c6c76ee982cb2d1e07edbb7fb2a53606630a1d810d5a47c9f646b708bf5