1
0
Fork 0
mirror of https://gitlab.com/bramw/baserow.git synced 2025-01-10 19:17:35 +00:00

Prepared for 1.22.1 release

This commit is contained in:
Bram Wiepjes 2023-12-21 14:21:19 +01:00
parent 28629b8a04
commit a2de9da42f
40 changed files with 138 additions and 128 deletions

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)
```bash
docker run -v baserow_data:/baserow/data -p 80:80 -p 443:443 baserow/baserow:1.22.0
docker run -v baserow_data:/baserow/data -p 80:80 -p 443:443 baserow/baserow:1.22.1
```
![Baserow screenshot](docs/assets/screenshot.png "Baserow screenshot")
@ -87,7 +87,7 @@ Created by Baserow B.V. - bram@baserow.io.
Distributes under the MIT license. See `LICENSE` for more information.
Version: 1.22.0
Version: 1.22.1
The official repository can be found at https://gitlab.com/baserow/baserow.

View file

@ -6,7 +6,7 @@ set -euo pipefail
# ENVIRONMENT VARIABLES USED DIRECTLY BY THIS ENTRYPOINT
# ======================================================
export BASEROW_VERSION="1.22.0"
export BASEROW_VERSION="1.22.1"
# Used by docker-entrypoint.sh to start the dev server
# If not configured you'll receive this: CommandError: "0.0.0.0:" is not a valid port number or address:port pair.

View file

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

View file

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

View file

@ -1 +1 @@
VERSION = "1.22.0"
VERSION = "1.22.1"

View file

@ -1,5 +1,11 @@
# Changelog
## Released 1.22.1
### Bug fixes
* Fix bug causing Baserow to use empty jwt secret by default when running baserow from docker compose. [#2160](https://gitlab.com/baserow/baserow/-/issues/2160)
## Released 1.22.0
### New features

View file

@ -1,5 +1,9 @@
{
"releases": [
{
"name": "1.22.1",
"created_at": "2023-12-21"
},
{
"name": "1.22.0",
"created_at": "2023-12-20"

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/).
```bash
docker run -v baserow_data:/baserow/data -p 80:80 -p 443:443 baserow/baserow:1.22.0
docker run -v baserow_data:/baserow/data -p 80:80 -p 443:443 baserow/baserow:1.22.1
```
## Quick Reference
@ -50,7 +50,7 @@ docker run \
-p 80:80 \
-p 443:443 \
--restart unless-stopped \
baserow/baserow:1.22.0
baserow/baserow:1.22.1
```
* Change `BASEROW_PUBLIC_URL` to `https://YOUR_DOMAIN` or `http://YOUR_IP` to enable
@ -72,7 +72,7 @@ docker run \
## Image Feature Overview
The `baserow/baserow:1.22.0` image by default runs all of Baserow's various services in a
The `baserow/baserow:1.22.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:
* Runs a Postgres database and Redis server by default internally and stores all data in
@ -115,7 +115,7 @@ docker run \
-p 80:80 \
-p 443:443 \
--restart unless-stopped \
baserow/baserow:1.22.0
baserow/baserow:1.22.1
```
### Behind a reverse proxy already handling ssl
@ -128,7 +128,7 @@ docker run \
-v baserow_data:/baserow/data \
-p 80:80 \
--restart unless-stopped \
baserow/baserow:1.22.0
baserow/baserow:1.22.1
```
### On a nonstandard HTTP port
@ -141,7 +141,7 @@ docker run \
-v baserow_data:/baserow/data \
-p 3001:80 \
--restart unless-stopped \
baserow/baserow:1.22.0
baserow/baserow:1.22.1
```
### With an external PostgresSQL server
@ -160,7 +160,7 @@ docker run \
-p 80:80 \
-p 443:443 \
--restart unless-stopped \
baserow/baserow:1.22.0
baserow/baserow:1.22.1
```
### With an external Redis server
@ -179,7 +179,7 @@ docker run \
-p 80:80 \
-p 443:443 \
--restart unless-stopped \
baserow/baserow:1.22.0
baserow/baserow:1.22.1
```
### With an external email server
@ -199,7 +199,7 @@ docker run \
-p 80:80 \
-p 443:443 \
--restart unless-stopped \
baserow/baserow:1.22.0
baserow/baserow:1.22.1
```
### Start just the embedded database
@ -212,7 +212,7 @@ docker run -it \
--name baserow \
-p 5432:5432 \
-v baserow_data:/baserow/data \
baserow/baserow:1.22.0 \
baserow/baserow:1.22.1 \
start-only-db
# Now get the password from
docker exec -it baserow cat /baserow/data/.pgpass
@ -230,7 +230,7 @@ docker run -it \
--rm \
--name baserow \
-v baserow_data:/baserow/data \
baserow/baserow:1.22.0 \
baserow/baserow:1.22.1 \
backend-cmd-with-db manage dbshell
```
@ -287,16 +287,16 @@ the command below.
```bash
# First read the help message for this command
docker run -it --rm -v baserow_data:/baserow/data baserow/baserow:1.22.0 \
docker run -it --rm -v baserow_data:/baserow/data baserow/baserow:1.22.1 \
backend-cmd-with-db backup
# 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.22.0 \
docker run -it --rm -v baserow_data:/baserow/data baserow/baserow:1.22.1 \
backend-cmd-with-db backup -f /baserow/data/backups/backup.tar.gz
# 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 \
baserow/baserow:1.22.0 backend-cmd-with-db backup -f /baserow/host/backup.tar.gz
baserow/baserow:1.22.1 backend-cmd-with-db backup -f /baserow/host/backup.tar.gz
```
### Restore only Baserow's Postgres Database
@ -365,7 +365,7 @@ docker run \
-p 80:80 \
-p 443:443 \
--restart unless-stopped \
baserow/baserow:1.22.0
baserow/baserow:1.22.1
```
Or you can just store it directly in the volume at `baserow_data/env` meaning it will
@ -374,7 +374,7 @@ be loaded whenever you mount in this data volume.
### Building your own image from Baserow
```dockerfile
FROM baserow/baserow:1.22.0
FROM baserow/baserow:1.22.1
# Any .sh files found in /baserow/supervisor/env/ will be sourced and loaded at startup
# useful for storing your own environment variable overrides.

View file

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

View file

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

View file

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

View file

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

View file

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

View file

@ -164,7 +164,7 @@ x-backend-variables: &backend-variables
services:
backend:
image: baserow/backend:1.22.0
image: baserow/backend:1.22.1
restart: unless-stopped
ports:
- "${HOST_PUBLISH_IP:-127.0.0.1}:8000:8000"
@ -179,7 +179,7 @@ services:
local:
web-frontend:
image: baserow/web-frontend:1.22.0
image: baserow/web-frontend:1.22.1
restart: unless-stopped
ports:
- "${HOST_PUBLISH_IP:-127.0.0.1}:3000:3000"
@ -212,7 +212,7 @@ services:
local:
celery:
image: baserow/backend:1.22.0
image: baserow/backend:1.22.1
restart: unless-stopped
environment:
<<: *backend-variables
@ -229,7 +229,7 @@ services:
local:
celery-export-worker:
image: baserow/backend:1.22.0
image: baserow/backend:1.22.1
restart: unless-stopped
command: celery-exportworker
environment:
@ -246,7 +246,7 @@ services:
local:
celery-beat-worker:
image: baserow/backend:1.22.0
image: baserow/backend:1.22.1
restart: unless-stopped
command: celery-beat
environment:

View file

@ -185,7 +185,7 @@ services:
local:
backend:
image: baserow/backend:1.22.0
image: baserow/backend:1.22.1
restart: unless-stopped
environment:
<<: *backend-variables
@ -198,7 +198,7 @@ services:
local:
web-frontend:
image: baserow/web-frontend:1.22.0
image: baserow/web-frontend:1.22.1
restart: unless-stopped
environment:
BASEROW_PUBLIC_URL: ${BASEROW_PUBLIC_URL-http://localhost}
@ -231,7 +231,7 @@ services:
local:
celery:
image: baserow/backend:1.22.0
image: baserow/backend:1.22.1
restart: unless-stopped
environment:
<<: *backend-variables
@ -248,7 +248,7 @@ services:
local:
celery-export-worker:
image: baserow/backend:1.22.0
image: baserow/backend:1.22.1
restart: unless-stopped
command: celery-exportworker
environment:
@ -265,7 +265,7 @@ services:
local:
celery-beat-worker:
image: baserow/backend:1.22.0
image: baserow/backend:1.22.1
restart: unless-stopped
command: celery-beat
environment:

View file

@ -3,7 +3,7 @@
If you have an [Apache server](https://www.apache.com/) this guide will explain how to
configure it to pass requests through to Baserow.
We strongly recommend you use our `baserow/baserow:1.22.0` image or the example
We strongly recommend you use our `baserow/baserow:1.22.1` image or the example
`docker-compose.yml` files (excluding the `.no-caddy.yml` variant) provided in
our [git repository](https://gitlab.com/baserow/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
> make sure you are using one of the two following deployment methods:
>
> * Your own container setup with our single service `baserow/backend:1.22.0`
and `baserow/web-frontend:1.22.0` images.
> * Your own container setup with our single service `baserow/backend:1.22.1`
and `baserow/web-frontend:1.22.1` images.
> * Or our `docker-compose.no-caddy.yml` example file in our [git repository](https://gitlab.com/baserow/baserow/-/tree/master/deploy/apache/).
>
> 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:
* The all-in-one Baserow image `baserow/baserow:1.22.0`
* The all-in-one Baserow image `baserow/baserow:1.22.1`
* Any of the example compose files found in the root of our git
repository `docker-compose.yml`/`docker-compose.local-build.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:
* Our standalone `baserow/backend:1.22.0` and `baserow/web-frontend:1.22.0` images with
* Our standalone `baserow/backend:1.22.1` and `baserow/web-frontend:1.22.1` images with
your own container orchestrator.
* Or the `docker-compose.no-caddy.yml` example docker compose file in the root of our
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
the rest of the guide we will use the example `/var/web` folder for this purpose.
If you are using the `baserow/backend:1.22.0` image then you can do this by adding
If you are using the `baserow/backend:1.22.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
Baserow backend.

View file

@ -3,7 +3,7 @@
If you have an [Nginx server](https://www.nginx.com/) this guide will explain how to
configure it to pass requests through to Baserow.
We strongly recommend you use our `baserow/baserow:1.22.0` image or the example
We strongly recommend you use our `baserow/baserow:1.22.1` image or the example
`docker-compose.yml` files (excluding the `.no-caddy.yml` variant) provided in
our [git repository](https://gitlab.com/baserow/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
> make sure you are using one of the two following deployment methods:
>
> * Your own container setup with our single service `baserow/backend:1.22.0`
and `baserow/web-frontend:1.22.0` images.
> * Your own container setup with our single service `baserow/backend:1.22.1`
and `baserow/web-frontend:1.22.1` images.
> * Or our `docker-compose.no-caddy.yml` example file in our [git repository](https://gitlab.com/baserow/baserow/-/tree/master/deploy/nginx/).
>
> 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:
* The all-in-one Baserow image `baserow/baserow:1.22.0`
* The all-in-one Baserow image `baserow/baserow:1.22.1`
* Any of the example compose files found in the root of our git
repository `docker-compose.yml`/`docker-compose.local-build.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:
* Our standalone `baserow/backend:1.22.0` and `baserow/web-frontend:1.22.0` images with
* Our standalone `baserow/backend:1.22.1` and `baserow/web-frontend:1.22.1` images with
your own container orchestrator.
* Or the `docker-compose.no-caddy.yml` example docker compose file in the root of our
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
the rest of the guide we will use the example `/var/web` folder for this purpose.
If you are using the `baserow/backend:1.22.0` image then you can do this by adding
If you are using the `baserow/backend:1.22.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
Baserow backend.

View file

@ -49,7 +49,7 @@ overview this is what any AWS deployment of Baserow will need:
## Option 1) Deploying the all-in-one image to Fargate/ECS
The `baserow/baserow:1.22.0` image runs all of Baserows various services inside the
The `baserow/baserow:1.22.1` image runs all of Baserows various services inside the
container for ease of use.
This image is designed for single server deployments or simple deployments to
@ -67,7 +67,7 @@ Run.
* You don't need to worry about configuring and linking together the different
services that make up a Baserow deployment.
* Configuring load balancers is easier as you can just directly route through all
requests to any horizontally scaled container running `baserow/baserow:1.22.0`.
requests to any horizontally scaled container running `baserow/baserow:1.22.1`.
#### Cons
@ -75,7 +75,7 @@ Run.
* Potentially higher resource usage overall as each of the all-in-one containers will
come with its internal services, so you have less granular control over scaling
specific services.
* For example if you deploy 10 `baserow/baserow:1.22.0` containers horizontally you
* For example if you deploy 10 `baserow/baserow:1.22.1` containers horizontally you
by default end up with:
* 10 web-frontend services
* 10 backend services
@ -188,18 +188,18 @@ Generally, the Redis server is not the bottleneck in Baserow deployments as they
Now create a target group on port 80 and ALB ready to route traffic to the Baserow
containers.
When setting up the health check for the ALB the `baserow/baserow:1.22.0` container
When setting up the health check for the ALB the `baserow/baserow:1.22.1` container
,which you'll be deploying next, choose port `80` and health check
URL `/api/_health/`. We recommend a long grace period of 900 seconds to account for
first-time migrations being run on the first container's startup.
#### 5) Launching Baserow on ECS/Fargate
Now we are ready to spin up our `baserow/baserow:1.22.0` containers. See below for a
Now we are ready to spin up our `baserow/baserow:1.22.1` containers. See below for a
full task definition and environment variables. We recommend launching the containers
with 2vCPUs and 4 GB of RAM each to start with. In short, you will want to:
1. Select the `baserow/baserow:1.22.0` image.
1. Select the `baserow/baserow:1.22.1` image.
2. Add a port mapping of `80` on TCP as this is where this images HTTP server is
listening by default.
3. Mark the container as essential.
@ -244,7 +244,7 @@ container_definitions = <<DEFINITION
[
{
"name": "baserow_task",
"image": "baserow/baserow:1.22.0",
"image": "baserow/baserow:1.22.1",
"logConfiguration": { #logs are not mandatory
"logDriver": "awslogs",
"options": {
@ -368,7 +368,7 @@ in-tool settings, active enterprise licenses, promote other users to being staff
## Option 2) Deploying Baserow as separate services to Fargate/ECS
The `baserow/backend:1.22.0` and `baserow/web-frontend:1.22.0` images allow you to run
The `baserow/backend:1.22.1` and `baserow/web-frontend:1.22.1` images allow you to run
Baserow's various services as separate containers.
These images are used by the community Helm chart, our various docker-compose.yml
@ -441,7 +441,7 @@ Alternatively [this docker-compose](https://gitlab.com/baserow/baserow/-/blob/de
This service is our HTTP REST API service. When creating the task definition you should:
1. In the task defintion use the `baserow/backend:1.22.0` image
1. In the task defintion use the `baserow/backend:1.22.1` image
2. Under docker configuration set `gunicorn-wsgi,--timeout,60` as the Command.
> We recommend setting the timeout of each HTTP API request to 60 seconds in the
@ -484,7 +484,7 @@ This service is our HTTP REST API service. When creating the task definition you
This service is our Websocket API service and when configuring the task definition you
should:
1. Use the `baserow/backend:1.22.0`
1. Use the `baserow/backend:1.22.1`
2. Under docker configuration set `gunicorn` as the Command.
3. We recommend 2vCPUs and 4 GB of RAM per container to start with.
4. Map the container port `8000`/`TCP`
@ -496,7 +496,7 @@ should:
This service is our asynchronous high priority task worker queue used for realtime
collaboration and sending emails.
1. Use the `baserow/backend:1.22.0` image with `celery-worker` as the image command.
1. Use the `baserow/backend:1.22.1` image with `celery-worker` as the image command.
2. Under docker configuration set `celery-worker` as the Command.
3. No port mappings needed.
4. We recommend 2vCPUs and 4 GB of RAM per container to start with.
@ -509,7 +509,7 @@ This service is our asynchronous slow/low priority task worker queue for batch
processes and running potentially slow operations for users like table exports and
imports etc.
1. Use the `baserow/backend:1.22.0` image.
1. Use the `baserow/backend:1.22.1` image.
2. Under docker configuration set `celery-exportworker` as the Command.
3. No port mappings needed.
4. We recommend 2vCPUs and 4 GB of RAM per container to start with.
@ -520,7 +520,7 @@ imports etc.
This service is our CRON task scheduler that can have multiple replicas deployed.
1. Use the `baserow/backend:1.22.0` image.
1. Use the `baserow/backend:1.22.1` image.
2. Under docker configuration set `celery-beat` as the Command.
3. No port mapping needed.
4. We recommend 1vCPUs and 3 GB of RAM per container to start with.
@ -537,7 +537,7 @@ This service is our CRON task scheduler that can have multiple replicas deployed
Finally, this service is used for server side rendering and serving the frontend of
Baserow.
1. Use the `baserow/web-frontend:1.22.0` image with no arguments needed.
1. Use the `baserow/web-frontend:1.22.1` image with no arguments needed.
2. Map the container port `3000`
3. We recommend 2vCPUs and 4 GB of RAM per container to start with.
4. Mark the container as essential.

View file

@ -46,7 +46,7 @@ $ cd baserow/deploy/cloudron
After that you can install the Baserow Cloudron app by executing the following commands.
```
$ cloudron install -l baserow.{YOUR_DOMAIN} --image baserow/cloudron:1.22.0
$ cloudron install -l baserow.{YOUR_DOMAIN} --image baserow/cloudron:1.22.1
App is being 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:
```
cloudron update --app {YOUR_APP_ID} --image baserow/cloudron:1.22.0
cloudron update --app {YOUR_APP_ID} --image baserow/cloudron:1.22.1
```
> Note that you must replace the image with the most recent image of Baserow. The

View file

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

View file

@ -10,9 +10,9 @@
Baserow consists of a number of services, two of which are built and provided as
separate standalone images by us:
* `baserow/backend:1.22.0` which by default starts the Gunicorn Django backend server
* `baserow/backend:1.22.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.
* `baserow/web-frontend:1.22.0` which is a Nuxt server providing Server Side rendering
* `baserow/web-frontend:1.22.1` which is a Nuxt server providing Server Side rendering
for the website.
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
images:
* `baserow/backend:1.22.0` (default command is `gunicorn`)
* `baserow/backend:1.22.0` with command `celery-worker`
* `baserow/backend:1.22.0` with command `celery-export-worker`
* `baserow/web-frontend:1.22.0` (default command is `nuxt-local`)
* `baserow/backend:1.22.1` (default command is `gunicorn`)
* `baserow/backend:1.22.1` with command `celery-worker`
* `baserow/backend:1.22.1` with command `celery-export-worker`
* `baserow/web-frontend:1.22.1` (default command is `nuxt-local`)
* A postgres database
* A redis server

View file

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

View file

@ -27,7 +27,7 @@ docker run \
-p 80:80 \
-p 443:443 \
--restart unless-stopped \
baserow/baserow:1.22.0
baserow/baserow:1.22.1
```
* Change `BASEROW_PUBLIC_URL` to `https://YOUR_DOMAIN` or `http://YOUR_IP` to enable
@ -50,7 +50,7 @@ docker run \
## Image Feature Overview
The `baserow/baserow:1.22.0` image by default runs all of Baserow's various services in
The `baserow/baserow:1.22.1` image by default runs all of Baserow's various services in
a single container for maximum ease of use.
> This image is designed for simple single server deployments or simple container
@ -156,7 +156,7 @@ docker run \
-p 80:80 \
-p 443:443 \
--restart unless-stopped \
baserow/baserow:1.22.0
baserow/baserow:1.22.1
```
### Behind a reverse proxy already handling ssl
@ -169,7 +169,7 @@ docker run \
-v baserow_data:/baserow/data \
-p 80:80 \
--restart unless-stopped \
baserow/baserow:1.22.0
baserow/baserow:1.22.1
```
### On a nonstandard HTTP port
@ -182,7 +182,7 @@ docker run \
-v baserow_data:/baserow/data \
-p 3001:80 \
--restart unless-stopped \
baserow/baserow:1.22.0
baserow/baserow:1.22.1
```
### With an external PostgresSQL server
@ -201,7 +201,7 @@ docker run \
-p 80:80 \
-p 443:443 \
--restart unless-stopped \
baserow/baserow:1.22.0
baserow/baserow:1.22.1
```
### With an external Redis server
@ -220,7 +220,7 @@ docker run \
-p 80:80 \
-p 443:443 \
--restart unless-stopped \
baserow/baserow:1.22.0
baserow/baserow:1.22.1
```
### With an external email server
@ -240,7 +240,7 @@ docker run \
-p 80:80 \
-p 443:443 \
--restart unless-stopped \
baserow/baserow:1.22.0
baserow/baserow:1.22.1
```
### With a Postgresql server running on the same host as the Baserow docker container
@ -278,7 +278,7 @@ docker run \
-v baserow_data:/baserow/data \
-p 80:80 \
-p 443:443 \
baserow/baserow:1.22.0
baserow/baserow:1.22.1
```
### Supply secrets using files
@ -305,7 +305,7 @@ docker run \
-v baserow_data:/baserow/data \
-p 80:80 \
-p 443:443 \
baserow/baserow:1.22.0
baserow/baserow:1.22.1
```
### Start just the embedded database
@ -318,7 +318,7 @@ docker run -it \
--name baserow \
-p 5432:5432 \
-v baserow_data:/baserow/data \
baserow/baserow:1.22.0 \
baserow/baserow:1.22.1 \
start-only-db
# Now get the password from
docker exec -it baserow cat /baserow/data/.pgpass
@ -336,7 +336,7 @@ docker run -it \
--rm \
--name baserow \
-v baserow_data:/baserow/data \
baserow/baserow:1.22.0 \
baserow/baserow:1.22.1 \
backend-cmd-with-db manage dbshell
```
@ -459,19 +459,19 @@ the command below.
```bash
# First read the help message for this command
docker run -it --rm -v baserow_data:/baserow/data baserow/baserow:1.22.0 \
docker run -it --rm -v baserow_data:/baserow/data baserow/baserow:1.22.1 \
backend-cmd-with-db backup --help
# Stop Baserow instance
docker stop baserow
# The command below backs up Baserow to the backups folder in the baserow_data volume:
docker run -it --rm -v baserow_data:/baserow/data baserow/baserow:1.22.0 \
docker run -it --rm -v baserow_data:/baserow/data baserow/baserow:1.22.1 \
backend-cmd-with-db backup -f /baserow/data/backups/backup.tar.gz
# 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 \
baserow/baserow:1.22.0 backend-cmd-with-db backup -f /baserow/host/backup.tar.gz
baserow/baserow:1.22.1 backend-cmd-with-db backup -f /baserow/host/backup.tar.gz
```
### Restore only Baserow's Postgres Database
@ -487,13 +487,13 @@ docker stop baserow
docker run -it --rm \
-v old_baserow_data_volume_containing_the_backup_tar_gz:/baserow/old_data \
-v new_baserow_data_volume_to_restore_into:/baserow/data \
baserow/baserow:1.22.0 backend-cmd-with-db restore -f /baserow/old_data/backup.tar.gz
baserow/baserow:1.22.1 backend-cmd-with-db restore -f /baserow/old_data/backup.tar.gz
# Or to restore from a file on your host instead run something like:
docker run -it --rm \
-v baserow_data:/baserow/data -v \
$(pwd):/baserow/host \
baserow/baserow:1.22.0 backend-cmd-with-db restore -f /baserow/host/backup.tar.gz
baserow/baserow:1.22.1 backend-cmd-with-db restore -f /baserow/host/backup.tar.gz
```
## Running healthchecks on Baserow
@ -544,7 +544,7 @@ docker run \
-p 80:80 \
-p 443:443 \
--restart unless-stopped \
baserow/baserow:1.22.0
baserow/baserow:1.22.1
```
Or you can just store it directly in the volume at `baserow_data/env` meaning it will be
@ -553,7 +553,7 @@ loaded whenever you mount in this data volume.
### Building your own image from Baserow
```dockerfile
FROM baserow/baserow:1.22.0
FROM baserow/baserow:1.22.1
# Any .sh files found in /baserow/supervisor/env/ will be sourced and loaded at startup
# useful for storing your own environment variable overrides.

View file

@ -165,7 +165,7 @@ spec:
topologyKey: "kubernetes.io/hostname"
containers:
- name: backend-asgi
image: baserow/backend:1.22.0
image: baserow/backend:1.22.1
workingDir: /baserow
args:
- "gunicorn"
@ -222,7 +222,7 @@ spec:
topologyKey: "kubernetes.io/hostname"
containers:
- name: backend-wsgi
image: baserow/backend:1.22.0
image: baserow/backend:1.22.1
workingDir: /baserow
args:
- "gunicorn-wsgi"
@ -281,7 +281,7 @@ spec:
topologyKey: "kubernetes.io/hostname"
containers:
- name: backend-worker
image: baserow/backend:1.22.0
image: baserow/backend:1.22.1
args:
- "celery-worker"
imagePullPolicy: Always
@ -298,7 +298,7 @@ spec:
- secretRef:
name: YOUR_ENV_SECRET_REF
- name: backend-export-worker
image: baserow/backend:1.22.0
image: baserow/backend:1.22.1
args:
- "celery-exportworker"
imagePullPolicy: Always
@ -315,7 +315,7 @@ spec:
- secretRef:
name: YOUR_ENV_SECRET_REF
- name: backend-beat-worker
image: baserow/backend:1.22.0
image: baserow/backend:1.22.1
args:
- "celery-beat"
imagePullPolicy: Always
@ -356,7 +356,7 @@ spec:
topologyKey: "kubernetes.io/hostname"
containers:
- name: web-frontend
image: baserow/web-frontend:1.22.0
image: baserow/web-frontend:1.22.1
args:
- nuxt
ports:

View file

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

View file

@ -10,7 +10,7 @@ Software versions are divided into the following groups:
## Web browsers
### Baserow 1.22.0
### Baserow 1.22.1
Browser | Supported versions | Recommended versions
----------------|--------------------|--------------------

View file

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

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`
```dockerfile
FROM baserow/baserow:1.22.0
FROM baserow/baserow:1.22.1
# You can install a plugin found in a git repo:
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
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:
`docker build -t my-customized-baserow:1.22.0 .`
`docker build -t my-customized-baserow:1.22.1 .`
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.22.0`
`docker run -p 80:80 -v baserow_data:/baserow/data my-customized-baserow:1.22.1`
### Installing in an existing Baserow all-in-one container
@ -111,7 +111,7 @@ docker run \
-v baserow_data:/baserow/data \
# ... All your normal launch args go here
-e BASEROW_PLUGIN_GIT_REPOS=https://example.com/example/plugin1.git,https://example.com/example/plugin2.git
baserow:1.22.0
baserow:1.22.1
```
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
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.22.0` image which does not
it, the new container is created from the `baserow/baserow:1.22.1` image which does not
have any plugins installed.
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
Baserow also provides `baserow/backend:1.22.0` and `baserow/web-frontend:1.22.0` images
Baserow also provides `baserow/backend:1.22.1` and `baserow/web-frontend:1.22.1` images
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
etc.
@ -145,8 +145,8 @@ used with docker run and a specified command and the plugin env vars shown above
example:
```
docker run --rm baserow/backend:1.22.0 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.22.0
docker run --rm baserow/backend:1.22.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.22.1
```
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)
for more details on how to do this.
2. Stop your Baserow server first - `docker stop baserow`
3. `docker run --rm -v baserow_data:/baserow/data baserow:1.22.0 uninstall-plugin plugin_name`
3. `docker run --rm -v baserow_data:/baserow/data baserow:1.22.1 uninstall-plugin plugin_name`
4. Now the plugin has uninstalled itself and all associated data has been removed.
5. Edit your custom `Dockerfile` and remove the plugin.
6. Rebuild your image - `docker build -t my-customized-baserow:1.22.0 .`
6. Rebuild your image - `docker build -t my-customized-baserow:1.22.1 .`
7. Remove the old container using the old image - `docker rm baserow`
8. Run your new image with the plugin removed
- `docker run -p 80:80 -v baserow_data:/baserow/data my-customized-baserow:1.22.0`
- `docker run -p 80:80 -v baserow_data:/baserow/data my-customized-baserow:1.22.1`
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
re-installed.
@ -207,7 +207,7 @@ associated data permanently.
restart as the environment variable will still contain the old plugin. To do this you
must:
1. `docker stop baserow`
2. `docker run --rm -v baserow_data:/baserow/data baserow:1.22.0 uninstall-plugin plugin_name`
2. `docker run --rm -v baserow_data:/baserow/data baserow:1.22.1 uninstall-plugin plugin_name`
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
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 \
--rm \
-v baserow_data:/baserow/data \
baserow:1.22.0 list-plugins
baserow:1.22.1 list-plugins
# or on a running container

View file

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

View file

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

View file

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

View file

@ -1,4 +1,4 @@
FROM baserow/backend:1.22.0
FROM baserow/backend:1.22.1
USER root

View file

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

View file

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

View file

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

View file

@ -1,4 +1,4 @@
FROM baserow/web-frontend:1.22.0
FROM baserow/web-frontend:1.22.1
USER root

View file

@ -2,7 +2,7 @@
# Bash strict mode: http://redsymbol.net/articles/unofficial-bash-strict-mode/
set -euo pipefail
export BASEROW_VERSION="1.22.0"
export BASEROW_VERSION="1.22.1"
BASEROW_WEBFRONTEND_PORT="${BASEROW_WEBFRONTEND_PORT:-3000}"
show_help() {

View file

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