archive/bramw_baserow
1
0
Fork 0
mirror of https://gitlab.com/bramw/baserow.git synced 2025-04-10 15:47:32 +00:00
Code Issues Projects Releases Wiki Activity

Bump to 1 12 1

Browse source
This commit is contained in:
Nigel Gott 2022-09-20 11:32:17 +00:00
parent 26aaeca0d5
commit 9a20931eb7
33 changed files with 120 additions and 112 deletions

4
README.md
View file

@ -17,7 +17,7 @@ tool gives you the powers of a developer without leaving your browser.
[![Deploy to Heroku](https://www.herokucdn.com/deploy/button.svg)](https://heroku.com/deploy?template=https://github.com/bram2w/baserow/tree/master) [![Deploy to Heroku](https://www.herokucdn.com/deploy/button.svg)](https://heroku.com/deploy?template=https://github.com/bram2w/baserow/tree/master)
```bash ```bash
docker run -v baserow_data:/baserow/data -p 80:80 -p 443:443 baserow/baserow:1.12.0 docker run -v baserow_data:/baserow/data -p 80:80 -p 443:443 baserow/baserow:1.12.1
``` ```
![Baserow screenshot](docs/assets/screenshot.png "Baserow screenshot") ![Baserow screenshot](docs/assets/screenshot.png "Baserow screenshot")
@ -90,7 +90,7 @@ Created by Baserow B.V. - bram@baserow.io.
Distributes under the MIT license. See `LICENSE` for more information. Distributes under the MIT license. See `LICENSE` for more information.
Version: 1.12.0 Version: 1.12.1
The official repository can be found at https://gitlab.com/bramw/baserow. The official repository can be found at https://gitlab.com/bramw/baserow.

2
backend/setup.py
View file

@ -5,7 +5,7 @@ from setuptools import find_packages, setup
PROJECT_DIR = os.path.dirname(__file__) PROJECT_DIR = os.path.dirname(__file__)
REQUIREMENTS_DIR = os.path.join(PROJECT_DIR, "requirements") REQUIREMENTS_DIR = os.path.join(PROJECT_DIR, "requirements")
VERSION = "1.12.0" VERSION = "1.12.1"
def get_requirements(env): def get_requirements(env):

2
backend/src/baserow/config/settings/base.py
View file

@ -301,7 +301,7 @@ SPECTACULAR_SETTINGS = {
"name": "MIT", "name": "MIT",
"url": "https://gitlab.com/bramw/baserow/-/blob/master/LICENSE", "url": "https://gitlab.com/bramw/baserow/-/blob/master/LICENSE",
}, },
"VERSION": "1.12.0", "VERSION": "1.12.1",
"SERVE_INCLUDE_SCHEMA": False, "SERVE_INCLUDE_SCHEMA": False,
"TAGS": [ "TAGS": [
{"name": "Settings"}, {"name": "Settings"},

2
backend/src/baserow/version.py
View file

@ -1 +1 @@
VERSION = "1.12.0" VERSION = "1.12.1"

14
changelog.md
View file

@ -9,9 +9,14 @@ For example:
## Unreleased ## Unreleased
* Always allow the cover image of a gallery view to be accessible by a public view [#1113](https://gitlab.com/bramw/baserow/-/issues/1113). ### New Features
* Added support for placeholders in form headings and fields. [#1168](https://gitlab.com/bramw/baserow/-/issues/1168)
* Fixed an issue where customers with malformed file extensions were unable to snapshot or duplicate properly [#1194](https://gitlab.com/bramw/baserow/-/issues/1194). ### Bug Fixes
### Refactors
## Released (2022-09-20 1.12.1)
### New Features ### New Features
@ -32,11 +37,14 @@ For example:
* Show database and table duplication progress in the left sidebar. [#1059](https://gitlab.com/bramw/baserow/-/issues/1059) * Show database and table duplication progress in the left sidebar. [#1059](https://gitlab.com/bramw/baserow/-/issues/1059)
* Add env vars for controlling which URLs and IPs webhooks are allowed to use. [#931](https://gitlab.com/bramw/baserow/-/issues/931) * Add env vars for controlling which URLs and IPs webhooks are allowed to use. [#931](https://gitlab.com/bramw/baserow/-/issues/931)
* Add a rich preview while importing data to an existing table. [#1120](https://gitlab.com/bramw/baserow/-/issues/1120) * Add a rich preview while importing data to an existing table. [#1120](https://gitlab.com/bramw/baserow/-/issues/1120)
* Always allow the cover image of a gallery view to be accessible by a public view [#1113](https://gitlab.com/bramw/baserow/-/issues/1113).
* Added support for placeholders in form headings and fields. [#1168](https://gitlab.com/bramw/baserow/-/issues/1168)
### Bug Fixes ### Bug Fixes
* Fixed Multiple Collaborators field renames. Now renaming the field won't recreate the field so that data is preserved. * Fixed Multiple Collaborators field renames. Now renaming the field won't recreate the field so that data is preserved.
* Fixed a bug that breaks the link row modal when a formula is referencing a single select field. [#1111](https://gitlab.com/bramw/baserow/-/issues/1111) * Fixed a bug that breaks the link row modal when a formula is referencing a single select field. [#1111](https://gitlab.com/bramw/baserow/-/issues/1111)
* Fixed an issue where customers with malformed file extensions were unable to snapshot or duplicate properly [#1194](https://gitlab.com/bramw/baserow/-/issues/1194).
### Refactors ### Refactors

32
deploy/all-in-one/README.md
View file

@ -15,7 +15,7 @@ tool gives you the powers of a developer without leaving your browser.
[Vue.js](https://vuejs.org/) and [PostgreSQL](https://www.postgresql.org/). [Vue.js](https://vuejs.org/) and [PostgreSQL](https://www.postgresql.org/).
```bash ```bash
docker run -v baserow_data:/baserow/data -p 80:80 -p 443:443 baserow/baserow:1.12.0 docker run -v baserow_data:/baserow/data -p 80:80 -p 443:443 baserow/baserow:1.12.1
``` ```
## Quick Reference ## Quick Reference
@ -49,7 +49,7 @@ docker run \
-p 80:80 \ -p 80:80 \
-p 443:443 \ -p 443:443 \
--restart unless-stopped \ --restart unless-stopped \
baserow/baserow:1.12.0 baserow/baserow:1.12.1
``` ```
* Change `BASEROW_PUBLIC_URL` to `https://YOUR_DOMAIN` or `http://YOUR_IP` to enable * Change `BASEROW_PUBLIC_URL` to `https://YOUR_DOMAIN` or `http://YOUR_IP` to enable
@ -71,7 +71,7 @@ docker run \
## Image Feature Overview ## Image Feature Overview
The `baserow/baserow:1.12.0` image by default runs all of Baserow's various services in a The `baserow/baserow:1.12.1` image by default runs all of Baserow's various services in a
single container for ease of use. A quick summary of its features are: single container for ease of use. A quick summary of its features are:
* Runs a Postgres database and Redis server by default internally and stores all data in * Runs a Postgres database and Redis server by default internally and stores all data in
@ -114,7 +114,7 @@ docker run \
-p 80:80 \ -p 80:80 \
-p 443:443 \ -p 443:443 \
--restart unless-stopped \ --restart unless-stopped \
baserow/baserow:1.12.0 baserow/baserow:1.12.1
``` ```
### Behind a reverse proxy already handling ssl ### Behind a reverse proxy already handling ssl
@ -127,7 +127,7 @@ docker run \
-v baserow_data:/baserow/data \ -v baserow_data:/baserow/data \
-p 80:80 \ -p 80:80 \
--restart unless-stopped \ --restart unless-stopped \
baserow/baserow:1.12.0 baserow/baserow:1.12.1
``` ```
### On a nonstandard HTTP port ### On a nonstandard HTTP port
@ -140,7 +140,7 @@ docker run \
-v baserow_data:/baserow/data \ -v baserow_data:/baserow/data \
-p 3001:80 \ -p 3001:80 \
--restart unless-stopped \ --restart unless-stopped \
baserow/baserow:1.12.0 baserow/baserow:1.12.1
``` ```
### With an external PostgresSQL server ### With an external PostgresSQL server
@ -159,7 +159,7 @@ docker run \
-p 80:80 \ -p 80:80 \
-p 443:443 \ -p 443:443 \
--restart unless-stopped \ --restart unless-stopped \
baserow/baserow:1.12.0 baserow/baserow:1.12.1
``` ```
### With an external Redis server ### With an external Redis server
@ -178,7 +178,7 @@ docker run \
-p 80:80 \ -p 80:80 \
-p 443:443 \ -p 443:443 \
--restart unless-stopped \ --restart unless-stopped \
baserow/baserow:1.12.0 baserow/baserow:1.12.1
``` ```
### With an external email server ### With an external email server
@ -198,7 +198,7 @@ docker run \
-p 80:80 \ -p 80:80 \
-p 443:443 \ -p 443:443 \
--restart unless-stopped \ --restart unless-stopped \
baserow/baserow:1.12.0 baserow/baserow:1.12.1
``` ```
### Start just the embedded database ### Start just the embedded database
@ -211,7 +211,7 @@ docker run -it \
--name baserow \ --name baserow \
-p 5432:5432 \ -p 5432:5432 \
-v baserow_data:/baserow/data \ -v baserow_data:/baserow/data \
baserow/baserow:1.12.0 \ baserow/baserow:1.12.1 \
start-only-db start-only-db
# Now get the password from # Now get the password from
docker exec -it baserow cat /baserow/data/.pgpass docker exec -it baserow cat /baserow/data/.pgpass
@ -229,7 +229,7 @@ docker run -it \
--rm \ --rm \
--name baserow \ --name baserow \
-v baserow_data:/baserow/data \ -v baserow_data:/baserow/data \
baserow/baserow:1.12.0 \ baserow/baserow:1.12.1 \
backend-cmd-with-db manage dbshell backend-cmd-with-db manage dbshell
``` ```
@ -286,16 +286,16 @@ the command below.
```bash ```bash
# First read the help message for this command # First read the help message for this command
docker run -it --rm -v baserow_data:/baserow/data baserow/baserow:1.12.0 \ docker run -it --rm -v baserow_data:/baserow/data baserow/baserow:1.12.1 \
backend-cmd-with-db backup backend-cmd-with-db backup
# By default backs up to the backups folder in the baserow_data volume. # By default backs up to the backups folder in the baserow_data volume.
docker run -it --rm -v baserow_data:/baserow/data baserow/baserow:1.12.0 \ docker run -it --rm -v baserow_data:/baserow/data baserow/baserow:1.12.1 \
backend-cmd-with-db backup -f /baserow/data/backups/backup.tar.gz backend-cmd-with-db backup -f /baserow/data/backups/backup.tar.gz
# Or backup to a file on your host instead run something like: # Or backup to a file on your host instead run something like:
docker run -it --rm -v baserow_data:/baserow/data -v $PWD:/baserow/host \ docker run -it --rm -v baserow_data:/baserow/data -v $PWD:/baserow/host \
baserow/baserow:1.12.0 backend-cmd-with-db backup -f /baserow/host/backup.tar.gz baserow/baserow:1.12.1 backend-cmd-with-db backup -f /baserow/host/backup.tar.gz
``` ```
### Restore only Baserow's Postgres Database ### Restore only Baserow's Postgres Database
@ -364,7 +364,7 @@ docker run \
-p 80:80 \ -p 80:80 \
-p 443:443 \ -p 443:443 \
--restart unless-stopped \ --restart unless-stopped \
baserow/baserow:1.12.0 baserow/baserow:1.12.1
``` ```
Or you can just store it directly in the volume at `baserow_data/env` meaning it will Or you can just store it directly in the volume at `baserow_data/env` meaning it will
@ -373,7 +373,7 @@ be loaded whenever you mount in this data volume.
### Building your own image from Baserow ### Building your own image from Baserow
```dockerfile ```dockerfile
FROM baserow/baserow:1.12.0 FROM baserow/baserow:1.12.1
# Any .sh files found in /baserow/supervisor/env/ will be sourced and loaded at startup # Any .sh files found in /baserow/supervisor/env/ will be sourced and loaded at startup
# useful for storing your own environment variable overrides. # useful for storing your own environment variable overrides.

2
deploy/all-in-one/supervisor/start.sh
View file

@ -14,7 +14,7 @@ cat << EOF
██████╔╝██║ ██║███████║███████╗██║ ██║╚██████╔╝╚███╔███╔╝ ██████╔╝██║ ██║███████║███████╗██║ ██║╚██████╔╝╚███╔███╔╝
╚═════╝ ╚═╝ ╚═╝╚══════╝╚══════╝╚═╝ ╚═╝ ╚═════╝ ╚══╝╚══╝ ╚═════╝ ╚═╝ ╚═╝╚══════╝╚══════╝╚═╝ ╚═╝ ╚═════╝ ╚══╝╚══╝
Version 1.12.0 Version 1.12.1
========================================================================================= =========================================================================================
EOF EOF

2
deploy/cloudron/CloudronManifest.json
View file

@ -8,7 +8,7 @@
"contactEmail": "bram@baserow.io", "contactEmail": "bram@baserow.io",
"icon": "file://logo.png", "icon": "file://logo.png",
"tags": ["no-code", "nocode", "database", "data", "collaborate", "airtable"], "tags": ["no-code", "nocode", "database", "data", "collaborate", "airtable"],
"version": "1.12.0", "version": "1.12.1",
"healthCheckPath": "/api/_health/", "healthCheckPath": "/api/_health/",
"httpPort": 80, "httpPort": 80,
"addons": { "addons": {

2
deploy/cloudron/Dockerfile
View file

@ -1,4 +1,4 @@
ARG FROM_IMAGE=baserow/baserow:1.12.0 ARG FROM_IMAGE=baserow/baserow:1.12.1
# This is pinned as version pinning is done by the CI setting FROM_IMAGE. # This is pinned as version pinning is done by the CI setting FROM_IMAGE.
# hadolint ignore=DL3006 # hadolint ignore=DL3006
FROM $FROM_IMAGE as image_base FROM $FROM_IMAGE as image_base

2
deploy/render/Dockerfile
View file

@ -1,4 +1,4 @@
ARG FROM_IMAGE=baserow/baserow:1.12.0 ARG FROM_IMAGE=baserow/baserow:1.12.1
# This is pinned as version pinning is done by the CI setting FROM_IMAGE. # This is pinned as version pinning is done by the CI setting FROM_IMAGE.
# hadolint ignore=DL3006 # hadolint ignore=DL3006
FROM $FROM_IMAGE as image_base FROM $FROM_IMAGE as image_base

2
docker-compose.all-in-one.yml
View file

@ -4,7 +4,7 @@ version: "3.4"
services: services:
baserow: baserow:
container_name: baserow container_name: baserow
image: baserow/baserow:1.12.0 image: baserow/baserow:1.12.1
environment: environment:
BASEROW_PUBLIC_URL: 'http://localhost' BASEROW_PUBLIC_URL: 'http://localhost'
ports: ports:

10
docker-compose.no-caddy.yml
View file

@ -126,7 +126,7 @@ x-backend-variables: &backend-variables
services: services:
backend: backend:
image: baserow/backend:1.12.0 image: baserow/backend:1.12.1
restart: unless-stopped restart: unless-stopped
ports: ports:
- "${HOST_PUBLISH_IP:-127.0.0.1}:8000:8000" - "${HOST_PUBLISH_IP:-127.0.0.1}:8000:8000"
@ -141,7 +141,7 @@ services:
local: local:
web-frontend: web-frontend:
image: baserow/web-frontend:1.12.0 image: baserow/web-frontend:1.12.1
restart: unless-stopped restart: unless-stopped
ports: ports:
- "${HOST_PUBLISH_IP:-127.0.0.1}:3000:3000" - "${HOST_PUBLISH_IP:-127.0.0.1}:3000:3000"
@ -166,7 +166,7 @@ services:
local: local:
celery: celery:
image: baserow/backend:1.12.0 image: baserow/backend:1.12.1
restart: unless-stopped restart: unless-stopped
environment: environment:
<<: *backend-variables <<: *backend-variables
@ -183,7 +183,7 @@ services:
local: local:
celery-export-worker: celery-export-worker:
image: baserow/backend:1.12.0 image: baserow/backend:1.12.1
restart: unless-stopped restart: unless-stopped
command: celery-exportworker command: celery-exportworker
environment: environment:
@ -200,7 +200,7 @@ services:
local: local:
celery-beat-worker: celery-beat-worker:
image: baserow/backend:1.12.0 image: baserow/backend:1.12.1
restart: unless-stopped restart: unless-stopped
command: celery-beat command: celery-beat
environment: environment:

10
docker-compose.yml
View file

@ -152,7 +152,7 @@ services:
local: local:
backend: backend:
image: baserow/backend:1.12.0 image: baserow/backend:1.12.1
restart: unless-stopped restart: unless-stopped
environment: environment:
<<: *backend-variables <<: *backend-variables
@ -165,7 +165,7 @@ services:
local: local:
web-frontend: web-frontend:
image: baserow/web-frontend:1.12.0 image: baserow/web-frontend:1.12.1
restart: unless-stopped restart: unless-stopped
environment: environment:
BASEROW_PUBLIC_URL: ${BASEROW_PUBLIC_URL-http://localhost} BASEROW_PUBLIC_URL: ${BASEROW_PUBLIC_URL-http://localhost}
@ -188,7 +188,7 @@ services:
local: local:
celery: celery:
image: baserow/backend:1.12.0 image: baserow/backend:1.12.1
restart: unless-stopped restart: unless-stopped
environment: environment:
<<: *backend-variables <<: *backend-variables
@ -205,7 +205,7 @@ services:
local: local:
celery-export-worker: celery-export-worker:
image: baserow/backend:1.12.0 image: baserow/backend:1.12.1
restart: unless-stopped restart: unless-stopped
command: celery-exportworker command: celery-exportworker
environment: environment:
@ -222,7 +222,7 @@ services:
local: local:
celery-beat-worker: celery-beat-worker:
image: baserow/backend:1.12.0 image: baserow/backend:1.12.1
restart: unless-stopped restart: unless-stopped
command: celery-beat command: celery-beat
environment: environment:

12
docs/installation/install-behind-apache.md
View file

@ -3,7 +3,7 @@
If you have an [Apache server](https://www.apache.com/) this guide will explain how to If you have an [Apache server](https://www.apache.com/) this guide will explain how to
configure it to pass requests through to Baserow. configure it to pass requests through to Baserow.
We strongly recommend you use our `baserow/baserow:1.12.0` image or the example We strongly recommend you use our `baserow/baserow:1.12.1` image or the example
`docker-compose.yml` files (excluding the `.no-caddy.yml` variant) provided in `docker-compose.yml` files (excluding the `.no-caddy.yml` variant) provided in
our [git repository](https://gitlab.com/bramw/baserow/-/tree/master/deploy/apache/). our [git repository](https://gitlab.com/bramw/baserow/-/tree/master/deploy/apache/).
@ -18,8 +18,8 @@ simplifies your life by:
> If you do not want to use our embedded Caddy service behind your Apache then > If you do not want to use our embedded Caddy service behind your Apache then
> make sure you are using one of the two following deployment methods: > make sure you are using one of the two following deployment methods:
> >
> * Your own container setup with our single service `baserow/backend:1.12.0` > * Your own container setup with our single service `baserow/backend:1.12.1`
and `baserow/web-frontend:1.12.0` images. and `baserow/web-frontend:1.12.1` images.
> * Or our `docker-compose.no-caddy.yml` example file in our [git repository](https://gitlab.com/bramw/baserow/-/tree/master/deploy/apache/). > * Or our `docker-compose.no-caddy.yml` example file in our [git repository](https://gitlab.com/bramw/baserow/-/tree/master/deploy/apache/).
> >
> Then you should use **Option 2: Without our embedded Caddy** section instead. > Then you should use **Option 2: Without our embedded Caddy** section instead.
@ -32,7 +32,7 @@ simplifies your life by:
Follow this option if you are using: Follow this option if you are using:
* The all-in-one Baserow image `baserow/baserow:1.12.0` * The all-in-one Baserow image `baserow/baserow:1.12.1`
* Any of the example compose files found in the root of our git * Any of the example compose files found in the root of our git
repository `docker-compose.yml`/`docker-compose.local-build.yml` repository `docker-compose.yml`/`docker-compose.local-build.yml`
/`docker-compose.all-in-one.yml` /`docker-compose.all-in-one.yml`
@ -116,7 +116,7 @@ You should now be able to access Baserow on you configured subdomain.
Follow this option if you are using: Follow this option if you are using:
* Our standalone `baserow/backend:1.12.0` and `baserow/web-frontend:1.12.0` images with * Our standalone `baserow/backend:1.12.1` and `baserow/web-frontend:1.12.1` images with
your own container orchestrator. your own container orchestrator.
* Or the `docker-compose.no-caddy.yml` example docker compose file in the root of our * Or the `docker-compose.no-caddy.yml` example docker compose file in the root of our
git repository. git repository.
@ -148,7 +148,7 @@ sudo systemctl restart apache2
You need to ensure user uploaded files are accessible in a folder for Apache to serve. In You need to ensure user uploaded files are accessible in a folder for Apache to serve. In
the rest of the guide we will use the example `/var/web` folder for this purpose. the rest of the guide we will use the example `/var/web` folder for this purpose.
If you are using the `baserow/backend:1.12.0` image then you can do this by adding If you are using the `baserow/backend:1.12.1` image then you can do this by adding
`-v /var/web:/baserow/data/media` to your normal `docker run` command used to launch the `-v /var/web:/baserow/data/media` to your normal `docker run` command used to launch the
Baserow backend. Baserow backend.

12
docs/installation/install-behind-nginx.md
View file

@ -3,7 +3,7 @@
If you have an [Nginx server](https://www.nginx.com/) this guide will explain how to If you have an [Nginx server](https://www.nginx.com/) this guide will explain how to
configure it to pass requests through to Baserow. configure it to pass requests through to Baserow.
We strongly recommend you use our `baserow/baserow:1.12.0` image or the example We strongly recommend you use our `baserow/baserow:1.12.1` image or the example
`docker-compose.yml` files (excluding the `.no-caddy.yml` variant) provided in `docker-compose.yml` files (excluding the `.no-caddy.yml` variant) provided in
our [git repository](https://gitlab.com/bramw/baserow/-/tree/master/deploy/nginx/). our [git repository](https://gitlab.com/bramw/baserow/-/tree/master/deploy/nginx/).
@ -18,8 +18,8 @@ simplifies your life by:
> If you do not want to use our embedded Caddy service behind your Nginx then > If you do not want to use our embedded Caddy service behind your Nginx then
> make sure you are using one of the two following deployment methods: > make sure you are using one of the two following deployment methods:
> >
> * Your own container setup with our single service `baserow/backend:1.12.0` > * Your own container setup with our single service `baserow/backend:1.12.1`
and `baserow/web-frontend:1.12.0` images. and `baserow/web-frontend:1.12.1` images.
> * Or our `docker-compose.no-caddy.yml` example file in our [git repository](https://gitlab.com/bramw/baserow/-/tree/master/deploy/nginx/). > * Or our `docker-compose.no-caddy.yml` example file in our [git repository](https://gitlab.com/bramw/baserow/-/tree/master/deploy/nginx/).
> >
> Then you should use **Option 2: Without our embedded Caddy** section instead. > Then you should use **Option 2: Without our embedded Caddy** section instead.
@ -32,7 +32,7 @@ simplifies your life by:
Follow this option if you are using: Follow this option if you are using:
* The all-in-one Baserow image `baserow/baserow:1.12.0` * The all-in-one Baserow image `baserow/baserow:1.12.1`
* Any of the example compose files found in the root of our git * Any of the example compose files found in the root of our git
repository `docker-compose.yml`/`docker-compose.local-build.yml` repository `docker-compose.yml`/`docker-compose.local-build.yml`
/`docker-compose.all-in-one.yml` /`docker-compose.all-in-one.yml`
@ -108,7 +108,7 @@ You should now be able to access Baserow on you configured subdomain.
Follow this option if you are using: Follow this option if you are using:
* Our standalone `baserow/backend:1.12.0` and `baserow/web-frontend:1.12.0` images with * Our standalone `baserow/backend:1.12.1` and `baserow/web-frontend:1.12.1` images with
your own container orchestrator. your own container orchestrator.
* Or the `docker-compose.no-caddy.yml` example docker compose file in the root of our * Or the `docker-compose.no-caddy.yml` example docker compose file in the root of our
git repository. git repository.
@ -127,7 +127,7 @@ but you might have to run different commands.
You need to ensure user uploaded files are accessible in a folder for Nginx to serve. In You need to ensure user uploaded files are accessible in a folder for Nginx to serve. In
the rest of the guide we will use the example `/var/web` folder for this purpose. the rest of the guide we will use the example `/var/web` folder for this purpose.
If you are using the `baserow/backend:1.12.0` image then you can do this by adding If you are using the `baserow/backend:1.12.1` image then you can do this by adding
`-v /var/web:/baserow/data/media` to your normal `docker run` command used to launch the `-v /var/web:/baserow/data/media` to your normal `docker run` command used to launch the
Baserow backend. Baserow backend.

4
docs/installation/install-on-cloudron.md
View file

@ -46,7 +46,7 @@ $ cd baserow/deploy/cloudron
After that you can install the Baserow Cloudron app by executing the following commands. After that you can install the Baserow Cloudron app by executing the following commands.
``` ```
$ cloudron install -l baserow.{YOUR_DOMAIN} --image baserow/cloudron:1.12.0 $ cloudron install -l baserow.{YOUR_DOMAIN} --image baserow/cloudron:1.12.1
App is being installed. App is being installed.
... ...
App is installed. App is installed.
@ -89,7 +89,7 @@ the `baserow/deploy/cloudron` folder, you can upgrade your cloudron baserow serv
the latest version by running the following command: the latest version by running the following command:
``` ```
cloudron update --app {YOUR_APP_ID} --image baserow/cloudron:1.12.0 cloudron update --app {YOUR_APP_ID} --image baserow/cloudron:1.12.1
``` ```
> Note that you must replace the image with the most recent image of Baserow. The > Note that you must replace the image with the most recent image of Baserow. The

4
docs/installation/install-on-ubuntu.md
View file

@ -34,7 +34,7 @@ docker run -e BASEROW_PUBLIC_URL=http://localhost \
-v baserow_data:/baserow/data \ -v baserow_data:/baserow/data \
-p 80:80 \ -p 80:80 \
-p 443:443 \ -p 443:443 \
baserow/baserow:1.12.0 baserow/baserow:1.12.1
# Watch the logs for Baserow to come available by running: # Watch the logs for Baserow to come available by running:
docker logs baserow docker logs baserow
``` ```
@ -147,7 +147,7 @@ docker run \
-v /baserow/media:/baserow/data/media \ -v /baserow/media:/baserow/data/media \
-p 80:80 \ -p 80:80 \
-p 443:443 \ -p 443:443 \
baserow/baserow:1.12.0 baserow/baserow:1.12.1
# Check the logs and wait for Baserow to become available # Check the logs and wait for Baserow to become available
docker logs baserow docker logs baserow
``` ```

12
docs/installation/install-using-standalone-images.md
View file

@ -10,9 +10,9 @@
Baserow consists of a number of services, two of which are built and provided as Baserow consists of a number of services, two of which are built and provided as
separate standalone images by us: separate standalone images by us:
* `baserow/backend:1.12.0` which by default starts the Gunicorn Django backend server * `baserow/backend:1.12.1` which by default starts the Gunicorn Django backend server
for Baserow but is also used to start the celery workers and celery beat services. for Baserow but is also used to start the celery workers and celery beat services.
* `baserow/web-frontend:1.12.0` which is a Nuxt server providing Server Side rendering * `baserow/web-frontend:1.12.1` which is a Nuxt server providing Server Side rendering
for the website. for the website.
If you want to use your own container orchestration software like Kubernetes then these If you want to use your own container orchestration software like Kubernetes then these
@ -27,10 +27,10 @@ in the root of our repository.
These are all the services you need to set up to run a Baserow using the standalone These are all the services you need to set up to run a Baserow using the standalone
images: images:
* `baserow/backend:1.12.0` (default command is `gunicorn`) * `baserow/backend:1.12.1` (default command is `gunicorn`)
* `baserow/backend:1.12.0` with command `celery-worker` * `baserow/backend:1.12.1` with command `celery-worker`
* `baserow/backend:1.12.0` with command `celery-export-worker` * `baserow/backend:1.12.1` with command `celery-export-worker`
* `baserow/web-frontend:1.12.0` (default command is `nuxt-local`) * `baserow/web-frontend:1.12.1` (default command is `nuxt-local`)
* A postgres database * A postgres database
* A redis server * A redis server

2
docs/installation/install-with-docker-compose.md
View file

@ -16,7 +16,7 @@ version: "3.4"
services: services:
baserow: baserow:
container_name: baserow container_name: baserow
image: baserow/baserow:1.12.0 image: baserow/baserow:1.12.1
environment: environment:
BASEROW_PUBLIC_URL: 'http://localhost' BASEROW_PUBLIC_URL: 'http://localhost'
ports: ports:

34
docs/installation/install-with-docker.md
View file

@ -27,7 +27,7 @@ docker run \
-p 80:80 \ -p 80:80 \
-p 443:443 \ -p 443:443 \
--restart unless-stopped \ --restart unless-stopped \
baserow/baserow:1.12.0 baserow/baserow:1.12.1
``` ```
* Change `BASEROW_PUBLIC_URL` to `https://YOUR_DOMAIN` or `http://YOUR_IP` to enable * Change `BASEROW_PUBLIC_URL` to `https://YOUR_DOMAIN` or `http://YOUR_IP` to enable
@ -50,7 +50,7 @@ docker run \
## Image Feature Overview ## Image Feature Overview
The `baserow/baserow:1.12.0` image by default runs all of Baserow's various services in a The `baserow/baserow:1.12.1` image by default runs all of Baserow's various services in a
single container for ease of use. A quick summary of its features are: single container for ease of use. A quick summary of its features are:
* Runs a Postgres database and Redis server by default internally and stores all data in * Runs a Postgres database and Redis server by default internally and stores all data in
@ -143,7 +143,7 @@ docker run \
-p 80:80 \ -p 80:80 \
-p 443:443 \ -p 443:443 \
--restart unless-stopped \ --restart unless-stopped \
baserow/baserow:1.12.0 baserow/baserow:1.12.1
``` ```
### Behind a reverse proxy already handling ssl ### Behind a reverse proxy already handling ssl
@ -156,7 +156,7 @@ docker run \
-v baserow_data:/baserow/data \ -v baserow_data:/baserow/data \
-p 80:80 \ -p 80:80 \
--restart unless-stopped \ --restart unless-stopped \
baserow/baserow:1.12.0 baserow/baserow:1.12.1
``` ```
### On a nonstandard HTTP port ### On a nonstandard HTTP port
@ -169,7 +169,7 @@ docker run \
-v baserow_data:/baserow/data \ -v baserow_data:/baserow/data \
-p 3001:80 \ -p 3001:80 \
--restart unless-stopped \ --restart unless-stopped \
baserow/baserow:1.12.0 baserow/baserow:1.12.1
``` ```
### With an external PostgresSQL server ### With an external PostgresSQL server
@ -188,7 +188,7 @@ docker run \
-p 80:80 \ -p 80:80 \
-p 443:443 \ -p 443:443 \
--restart unless-stopped \ --restart unless-stopped \
baserow/baserow:1.12.0 baserow/baserow:1.12.1
``` ```
### With an external Redis server ### With an external Redis server
@ -207,7 +207,7 @@ docker run \
-p 80:80 \ -p 80:80 \
-p 443:443 \ -p 443:443 \
--restart unless-stopped \ --restart unless-stopped \
baserow/baserow:1.12.0 baserow/baserow:1.12.1
``` ```
### With an external email server ### With an external email server
@ -227,7 +227,7 @@ docker run \
-p 80:80 \ -p 80:80 \
-p 443:443 \ -p 443:443 \
--restart unless-stopped \ --restart unless-stopped \
baserow/baserow:1.12.0 baserow/baserow:1.12.1
``` ```
### With a Postgresql server running on the same host as the Baserow docker container ### With a Postgresql server running on the same host as the Baserow docker container
@ -265,7 +265,7 @@ docker run \
-v baserow_data:/baserow/data \ -v baserow_data:/baserow/data \
-p 80:80 \ -p 80:80 \
-p 443:443 \ -p 443:443 \
baserow/baserow:1.12.0 baserow/baserow:1.12.1
``` ```
### Supply secrets using files ### Supply secrets using files
@ -292,7 +292,7 @@ docker run \
-v baserow_data:/baserow/data \ -v baserow_data:/baserow/data \
-p 80:80 \ -p 80:80 \
-p 443:443 \ -p 443:443 \
baserow/baserow:1.12.0 baserow/baserow:1.12.1
``` ```
### Start just the embedded database ### Start just the embedded database
@ -305,7 +305,7 @@ docker run -it \
--name baserow \ --name baserow \
-p 5432:5432 \ -p 5432:5432 \
-v baserow_data:/baserow/data \ -v baserow_data:/baserow/data \
baserow/baserow:1.12.0 \ baserow/baserow:1.12.1 \
start-only-db start-only-db
# Now get the password from # Now get the password from
docker exec -it baserow cat /baserow/data/.pgpass docker exec -it baserow cat /baserow/data/.pgpass
@ -323,7 +323,7 @@ docker run -it \
--rm \ --rm \
--name baserow \ --name baserow \
-v baserow_data:/baserow/data \ -v baserow_data:/baserow/data \
baserow/baserow:1.12.0 \ baserow/baserow:1.12.1 \
backend-cmd-with-db manage dbshell backend-cmd-with-db manage dbshell
``` ```
@ -379,16 +379,16 @@ the command below.
```bash ```bash
# First read the help message for this command # First read the help message for this command
docker run -it --rm -v baserow_data:/baserow/data baserow/baserow:1.12.0 \ docker run -it --rm -v baserow_data:/baserow/data baserow/baserow:1.12.1 \
backend-cmd-with-db backup backend-cmd-with-db backup
# By default backs up to the backups folder in the baserow_data volume. # By default backs up to the backups folder in the baserow_data volume.
docker run -it --rm -v baserow_data:/baserow/data baserow/baserow:1.12.0 \ docker run -it --rm -v baserow_data:/baserow/data baserow/baserow:1.12.1 \
backend-cmd-with-db backup -f /baserow/data/backups/backup.tar.gz backend-cmd-with-db backup -f /baserow/data/backups/backup.tar.gz
# Or backup to a file on your host instead run something like: # Or backup to a file on your host instead run something like:
docker run -it --rm -v baserow_data:/baserow/data -v $PWD:/baserow/host \ docker run -it --rm -v baserow_data:/baserow/data -v $PWD:/baserow/host \
baserow/baserow:1.12.0 backend-cmd-with-db backup -f /baserow/host/backup.tar.gz baserow/baserow:1.12.1 backend-cmd-with-db backup -f /baserow/host/backup.tar.gz
``` ```
### Restore only Baserow's Postgres Database ### Restore only Baserow's Postgres Database
@ -457,7 +457,7 @@ docker run \
-p 80:80 \ -p 80:80 \
-p 443:443 \ -p 443:443 \
--restart unless-stopped \ --restart unless-stopped \
baserow/baserow:1.12.0 baserow/baserow:1.12.1
``` ```
Or you can just store it directly in the volume at `baserow_data/env` meaning it will be Or you can just store it directly in the volume at `baserow_data/env` meaning it will be
@ -466,7 +466,7 @@ loaded whenever you mount in this data volume.
### Building your own image from Baserow ### Building your own image from Baserow
```dockerfile ```dockerfile
FROM baserow/baserow:1.12.0 FROM baserow/baserow:1.12.1
# Any .sh files found in /baserow/supervisor/env/ will be sourced and loaded at startup # Any .sh files found in /baserow/supervisor/env/ will be sourced and loaded at startup
# useful for storing your own environment variable overrides. # useful for storing your own environment variable overrides.

12
docs/installation/install-with-k8s.md
View file

@ -156,7 +156,7 @@ spec:
topologyKey: "kubernetes.io/hostname" topologyKey: "kubernetes.io/hostname"
containers: containers:
- name: backend-asgi - name: backend-asgi
image: baserow/backend:1.12.0 image: baserow/backend:1.12.1
workingDir: /baserow workingDir: /baserow
args: args:
- "gunicorn" - "gunicorn"
@ -213,7 +213,7 @@ spec:
topologyKey: "kubernetes.io/hostname" topologyKey: "kubernetes.io/hostname"
containers: containers:
- name: backend-wsgi - name: backend-wsgi
image: baserow/backend:1.12.0 image: baserow/backend:1.12.1
workingDir: /baserow workingDir: /baserow
args: args:
- "gunicorn-wsgi" - "gunicorn-wsgi"
@ -272,7 +272,7 @@ spec:
topologyKey: "kubernetes.io/hostname" topologyKey: "kubernetes.io/hostname"
containers: containers:
- name: backend-worker - name: backend-worker
image: baserow/backend:1.12.0 image: baserow/backend:1.12.1
args: args:
- "celery-worker" - "celery-worker"
imagePullPolicy: Always imagePullPolicy: Always
@ -289,7 +289,7 @@ spec:
- secretRef: - secretRef:
name: YOUR_ENV_SECRET_REF name: YOUR_ENV_SECRET_REF
- name: backend-export-worker - name: backend-export-worker
image: baserow/backend:1.12.0 image: baserow/backend:1.12.1
args: args:
- "celery-exportworker" - "celery-exportworker"
imagePullPolicy: Always imagePullPolicy: Always
@ -306,7 +306,7 @@ spec:
- secretRef: - secretRef:
name: YOUR_ENV_SECRET_REF name: YOUR_ENV_SECRET_REF
- name: backend-beat-worker - name: backend-beat-worker
image: baserow/backend:1.12.0 image: baserow/backend:1.12.1
args: args:
- "celery-beat" - "celery-beat"
imagePullPolicy: Always imagePullPolicy: Always
@ -347,7 +347,7 @@ spec:
topologyKey: "kubernetes.io/hostname" topologyKey: "kubernetes.io/hostname"
containers: containers:
- name: web-frontend - name: web-frontend
image: baserow/web-frontend:1.12.0 image: baserow/web-frontend:1.12.1
args: args:
- nuxt - nuxt
ports: ports:

2
docs/installation/install-with-traefik.md
View file

@ -11,7 +11,7 @@ See below for an example docker-compose file that will enable Baserow with Traef
version: "3.4" version: "3.4"
services: services:
baserow: baserow:
image: baserow/baserow:1.12.0 image: baserow/baserow:1.12.1
container_name: baserow container_name: baserow
labels: labels:
# Explicitly tell Traefik to expose this container # Explicitly tell Traefik to expose this container

2
docs/plugins/creation.md
View file

@ -122,7 +122,7 @@ containing metadata about your plugin. It should have the following JSON structu
{ {
"name": "TODO", "name": "TODO",
"version": "TODO", "version": "TODO",
"supported_baserow_versions": "1.12.0", "supported_baserow_versions": "1.12.1",
"plugin_api_version": "0.0.1-alpha", "plugin_api_version": "0.0.1-alpha",
"description": "TODO", "description": "TODO",
"author": "TODO", "author": "TODO",

26
docs/plugins/installation.md
View file

@ -36,7 +36,7 @@ build your own image based off the Baserow all-in-one image.
4. Next copy the contents shown into your `Dockerfile` 4. Next copy the contents shown into your `Dockerfile`
```dockerfile ```dockerfile
FROM baserow/baserow:1.12.0 FROM baserow/baserow:1.12.1
# You can install a plugin found in a git repo: # You can install a plugin found in a git repo:
RUN /baserow/plugins/install_plugin.sh \ RUN /baserow/plugins/install_plugin.sh \
@ -70,9 +70,9 @@ RUN /baserow/plugins/install_plugin.sh \
5. Choose which of the `RUN` commands you'd like to use to install your plugins and 5. Choose which of the `RUN` commands you'd like to use to install your plugins and
delete the rest, replace the example URLs with ones pointing to your plugin. delete the rest, replace the example URLs with ones pointing to your plugin.
6. Now build your custom Baserow with the plugin installed by running: 6. Now build your custom Baserow with the plugin installed by running:
`docker build -t my-customized-baserow:1.12.0 .` `docker build -t my-customized-baserow:1.12.1 .`
7. Finally, you can run your new customized image just like the normal Baserow image: 7. Finally, you can run your new customized image just like the normal Baserow image:
`docker run -p 80:80 -v baserow_data:/baserow/data my-customized-baserow:1.12.0` `docker run -p 80:80 -v baserow_data:/baserow/data my-customized-baserow:1.12.1`
### Installing in an existing Baserow all-in-one container ### Installing in an existing Baserow all-in-one container
@ -111,7 +111,7 @@ docker run \
-v baserow_data:/baserow/data \ -v baserow_data:/baserow/data \
# ... All your normal launch args go here # ... All your normal launch args go here
-e BASEROW_PLUGIN_GIT_REPOS=https://example.com/example/plugin1.git,https://example.com/example/plugin2.git -e BASEROW_PLUGIN_GIT_REPOS=https://example.com/example/plugin1.git,https://example.com/example/plugin2.git
baserow:1.12.0 baserow:1.12.1
``` ```
These variables will only trigger and installation when found on startup of the These variables will only trigger and installation when found on startup of the
@ -120,7 +120,7 @@ container. To uninstall a plugin you must still manually follow the instructions
### Caveats when installing into an existing container ### Caveats when installing into an existing container
If you ever delete the container you've installed plugins into at runtime and re-create If you ever delete the container you've installed plugins into at runtime and re-create
it, the new container is created from the `baserow/baserow:1.12.0` image which does not it, the new container is created from the `baserow/baserow:1.12.1` image which does not
have any plugins installed. have any plugins installed.
However, when a plugin is installed at runtime or build time it is stored in the However, when a plugin is installed at runtime or build time it is stored in the
@ -135,7 +135,7 @@ scratch.
### Installing into standalone Baserow service images ### Installing into standalone Baserow service images
Baserow also provides `baserow/backend:1.12.0` and `baserow/web-frontend:1.12.0` images Baserow also provides `baserow/backend:1.12.1` and `baserow/web-frontend:1.12.1` images
which only run the respective backend/celery/web-frontend services. These images are which only run the respective backend/celery/web-frontend services. These images are
used for more advanced self-hosted deployments like a multi-service docker-compose, k8s used for more advanced self-hosted deployments like a multi-service docker-compose, k8s
etc. etc.
@ -145,8 +145,8 @@ used with docker run and a specified command and the plugin env vars shown above
example: example:
``` ```
docker run --rm baserow/backend:1.12.0 install-plugin ... docker run --rm baserow/backend:1.12.1 install-plugin ...
docker run -e BASEROW_PLUGIN_GIT_REPOS=https://example.com/example/plugin1.git,https://example.com/example/plugin2.git --rm baserow/backend:1.12.0 docker run -e BASEROW_PLUGIN_GIT_REPOS=https://example.com/example/plugin1.git,https://example.com/example/plugin2.git --rm baserow/backend:1.12.1
``` ```
You can use these scripts exactly as you would in the sections above to install a plugin You can use these scripts exactly as you would in the sections above to install a plugin
@ -169,13 +169,13 @@ associated data permanently.
[Docker install guide backup section](../installation/install-with-docker.md) [Docker install guide backup section](../installation/install-with-docker.md)
for more details on how to do this. for more details on how to do this.
2. Stop your Baserow server first - `docker stop baserow` 2. Stop your Baserow server first - `docker stop baserow`
3. `docker run --rm -v baserow_data:/baserow/data baserow:1.12.0 uninstall-plugin plugin_name` 3. `docker run --rm -v baserow_data:/baserow/data baserow:1.12.1 uninstall-plugin plugin_name`
4. Now the plugin has uninstalled itself and all associated data has been removed. 4. Now the plugin has uninstalled itself and all associated data has been removed.
5. Edit your custom `Dockerfile` and remove the plugin. 5. Edit your custom `Dockerfile` and remove the plugin.
6. Rebuild your image - `docker build -t my-customized-baserow:1.12.0 .` 6. Rebuild your image - `docker build -t my-customized-baserow:1.12.1 .`
7. Remove the old container using the old image - `docker rm baserow` 7. Remove the old container using the old image - `docker rm baserow`
8. Run your new image with the plugin removed 8. Run your new image with the plugin removed
- `docker run -p 80:80 -v baserow_data:/baserow/data my-customized-baserow:1.12.0` - `docker run -p 80:80 -v baserow_data:/baserow/data my-customized-baserow:1.12.1`
9. If you fail to do this if you ever recreate the container, your custom image still 9. If you fail to do this if you ever recreate the container, your custom image still
has the plugin installed and the new container will start up again with the plugin has the plugin installed and the new container will start up again with the plugin
re-installed. re-installed.
@ -207,7 +207,7 @@ associated data permanently.
restart as the environment variable will still contain the old plugin. To do this you restart as the environment variable will still contain the old plugin. To do this you
must: must:
1. `docker stop baserow` 1. `docker stop baserow`
2. `docker run --rm -v baserow_data:/baserow/data baserow:1.12.0 uninstall-plugin plugin_name` 2. `docker run --rm -v baserow_data:/baserow/data baserow:1.12.1 uninstall-plugin plugin_name`
3. Now the plugin has uninstalled itself and all associated data has been removed. 3. Now the plugin has uninstalled itself and all associated data has been removed.
4. Finally, recreate your Baserow container by using the same `docker run` command 4. Finally, recreate your Baserow container by using the same `docker run` command
you launched it with, just make sure the plugin you uninstalled has been removed you launched it with, just make sure the plugin you uninstalled has been removed
@ -222,7 +222,7 @@ check what plugins are currently installed.
docker run \ docker run \
--rm \ --rm \
-v baserow_data:/baserow/data \ -v baserow_data:/baserow/data \
baserow:1.12.0 list-plugins baserow:1.12.1 list-plugins
# or on a running container # or on a running container

2
heroku.Dockerfile
View file

@ -1,4 +1,4 @@
ARG FROM_IMAGE=baserow/baserow:1.12.0 ARG FROM_IMAGE=baserow/baserow:1.12.1
# This is pinned as version pinning is done by the CI setting FROM_IMAGE. # This is pinned as version pinning is done by the CI setting FROM_IMAGE.
# hadolint ignore=DL3006 # hadolint ignore=DL3006
FROM $FROM_IMAGE as image_base FROM $FROM_IMAGE as image_base

2
plugin-boilerplate/{{ cookiecutter.project_slug }}/Dockerfile
View file

@ -1,4 +1,4 @@
FROM baserow/baserow:1.12.0 FROM baserow/baserow:1.12.1
COPY ./plugins/{{ cookiecutter.project_module }}/ /baserow/plugins/{{ cookiecutter.project_module }}/ COPY ./plugins/{{ cookiecutter.project_module }}/ /baserow/plugins/{{ cookiecutter.project_module }}/
RUN /baserow/plugins/install_plugin.sh --folder /baserow/plugins/{{ cookiecutter.project_module }} RUN /baserow/plugins/install_plugin.sh --folder /baserow/plugins/{{ cookiecutter.project_module }}

4
plugin-boilerplate/{{ cookiecutter.project_slug }}/backend-dev.Dockerfile
View file

@ -1,7 +1,7 @@
# This a dev image for testing your plugin when installed into the Baserow backend image # This a dev image for testing your plugin when installed into the Baserow backend image
FROM baserow/backend:1.12.0 as base FROM baserow/backend:1.12.1 as base
FROM baserow/backend:1.12.0 FROM baserow/backend:1.12.1
USER root USER root

2
plugin-boilerplate/{{ cookiecutter.project_slug }}/backend.Dockerfile
View file

@ -1,4 +1,4 @@
FROM baserow/backend:1.12.0 FROM baserow/backend:1.12.1
USER root USER root

4
plugin-boilerplate/{{ cookiecutter.project_slug }}/dev.Dockerfile
View file

@ -1,7 +1,7 @@
# This a dev image for testing your plugin when installed into the Baserow all-in-one image # This a dev image for testing your plugin when installed into the Baserow all-in-one image
FROM baserow/baserow:1.12.0 as base FROM baserow/baserow:1.12.1 as base
FROM baserow/baserow:1.12.0 FROM baserow/baserow:1.12.1
ARG PLUGIN_BUILD_UID ARG PLUGIN_BUILD_UID
ENV PLUGIN_BUILD_UID=${PLUGIN_BUILD_UID:-9999} ENV PLUGIN_BUILD_UID=${PLUGIN_BUILD_UID:-9999}

2
plugin-boilerplate/{{ cookiecutter.project_slug }}/plugins/{{ cookiecutter.project_module }}/baserow_plugin_info.json
View file

@ -1,7 +1,7 @@
{ {
"name": "{{ cookiecutter.project_name }}", "name": "{{ cookiecutter.project_name }}",
"version": "0.0.1", "version": "0.0.1",
"supported_baserow_versions": "1.12.0", "supported_baserow_versions": "1.12.1",
"plugin_api_version": "0.0.1-alpha", "plugin_api_version": "0.0.1-alpha",
"description": "TODO", "description": "TODO",
"author": "TODO", "author": "TODO",

4
plugin-boilerplate/{{ cookiecutter.project_slug }}/web-frontend-dev.Dockerfile
View file

@ -1,6 +1,6 @@
# This a dev image for testing your plugin when installed into the Baserow web-frontend image # This a dev image for testing your plugin when installed into the Baserow web-frontend image
FROM baserow/web-frontend:1.12.0 as base FROM baserow/web-frontend:1.12.1 as base
FROM baserow/web-frontend:1.12.0 FROM baserow/web-frontend:1.12.1
USER root USER root

2
plugin-boilerplate/{{ cookiecutter.project_slug }}/web-frontend.Dockerfile
View file

@ -1,4 +1,4 @@
FROM baserow/web-frontend:1.12.0 FROM baserow/web-frontend:1.12.1
USER root USER root

2
web-frontend/package.json
View file

@ -1,6 +1,6 @@
{ {
"name": "baserow", "name": "baserow",
"version": "1.12.0", "version": "1.12.1",
"private": true, "private": true,
"description": "Baserow: open source no-code database web frontend.", "description": "Baserow: open source no-code database web frontend.",
"author": "Bram Wiepjes (Baserow)", "author": "Bram Wiepjes (Baserow)",