mirror of
https://gitlab.com/bramw/baserow.git
synced 2025-04-04 21:25:24 +00:00
Bump to 1.13.3
This commit is contained in:
Nigel Gott
parent
33e0933538
commit
7dfc41d224
33 changed files with 117 additions and 109 deletions
README.mdheroku.Dockerfile
backend
changelog.mddeploy
docker-compose.all-in-one.ymldocker-compose.no-caddy.ymldocker-compose.ymldocs
installation
install-behind-apache.mdinstall-behind-nginx.mdinstall-on-cloudron.mdinstall-on-ubuntu.mdinstall-using-standalone-images.mdinstall-with-docker-compose.mdinstall-with-docker.mdinstall-with-k8s.mdinstall-with-traefik.md
plugins
plugin-boilerplate/{{ cookiecutter.project_slug }}
Dockerfilebackend-dev.Dockerfilebackend.Dockerfiledev.Dockerfile
plugins/{{ cookiecutter.project_module }}
web-frontend-dev.Dockerfileweb-frontend.Dockerfileweb-frontend
|
|
@ -17,7 +17,7 @@ tool gives you the powers of a developer without leaving your browser.
|
|||
[](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.13.2
|
||||
docker run -v baserow_data:/baserow/data -p 80:80 -p 443:443 baserow/baserow:1.13.3
|
||||
```
|
||||
|
||||
|
||||
|
|
@ -90,7 +90,7 @@ Created by Baserow B.V. - bram@baserow.io.
|
|||
|
||||
Distributes under the MIT license. See `LICENSE` for more information.
|
||||
|
||||
Version: 1.13.2
|
||||
Version: 1.13.3
|
||||
|
||||
The official repository can be found at https://gitlab.com/bramw/baserow.
|
||||
|
||||
|
|
|
|||
|
|
@ -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.13.2"
|
||||
VERSION = "1.13.3"
|
||||
|
||||
|
||||
def get_requirements(env):
|
||||
|
|
|
|||
|
|
@ -316,7 +316,7 @@ SPECTACULAR_SETTINGS = {
|
|||
"name": "MIT",
|
||||
"url": "https://gitlab.com/bramw/baserow/-/blob/master/LICENSE",
|
||||
},
|
||||
"VERSION": "1.13.2",
|
||||
"VERSION": "1.13.3",
|
||||
"SERVE_INCLUDE_SCHEMA": False,
|
||||
"TAGS": [
|
||||
{"name": "Settings"},
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
VERSION = "1.13.2"
|
||||
VERSION = "1.13.3"
|
||||
|
|
|
|||
|
|
@ -9,6 +9,14 @@ For example:
|
|||
|
||||
## Unreleased
|
||||
|
||||
### New Features
|
||||
|
||||
### Bug Fixes
|
||||
|
||||
### Refactors
|
||||
|
||||
## Released (2022-12-21 1.13.3)
|
||||
|
||||
## Deploy steps
|
||||
* (Optional) - Regenerate the `card_cover` thumbnails to have better quality images in gallery views with: `./baserow regenerate_user_file_thumbnails card_cover`
|
||||
|
||||
|
|
|
|||
|
|
@ -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.13.2
|
||||
docker run -v baserow_data:/baserow/data -p 80:80 -p 443:443 baserow/baserow:1.13.3
|
||||
```
|
||||
|
||||
## Quick Reference
|
||||
|
|
@ -50,7 +50,7 @@ docker run \
|
|||
-p 80:80 \
|
||||
-p 443:443 \
|
||||
--restart unless-stopped \
|
||||
baserow/baserow:1.13.2
|
||||
baserow/baserow:1.13.3
|
||||
```
|
||||
|
||||
* 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.13.2` image by default runs all of Baserow's various services in a
|
||||
The `baserow/baserow:1.13.3` 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.13.2
|
||||
baserow/baserow:1.13.3
|
||||
```
|
||||
|
||||
### 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.13.2
|
||||
baserow/baserow:1.13.3
|
||||
```
|
||||
|
||||
### 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.13.2
|
||||
baserow/baserow:1.13.3
|
||||
```
|
||||
|
||||
### With an external PostgresSQL server
|
||||
|
|
@ -160,7 +160,7 @@ docker run \
|
|||
-p 80:80 \
|
||||
-p 443:443 \
|
||||
--restart unless-stopped \
|
||||
baserow/baserow:1.13.2
|
||||
baserow/baserow:1.13.3
|
||||
```
|
||||
|
||||
### With an external Redis server
|
||||
|
|
@ -179,7 +179,7 @@ docker run \
|
|||
-p 80:80 \
|
||||
-p 443:443 \
|
||||
--restart unless-stopped \
|
||||
baserow/baserow:1.13.2
|
||||
baserow/baserow:1.13.3
|
||||
```
|
||||
|
||||
### With an external email server
|
||||
|
|
@ -199,7 +199,7 @@ docker run \
|
|||
-p 80:80 \
|
||||
-p 443:443 \
|
||||
--restart unless-stopped \
|
||||
baserow/baserow:1.13.2
|
||||
baserow/baserow:1.13.3
|
||||
```
|
||||
|
||||
### 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.13.2 \
|
||||
baserow/baserow:1.13.3 \
|
||||
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.13.2 \
|
||||
baserow/baserow:1.13.3 \
|
||||
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.13.2 \
|
||||
docker run -it --rm -v baserow_data:/baserow/data baserow/baserow:1.13.3 \
|
||||
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.13.2 \
|
||||
docker run -it --rm -v baserow_data:/baserow/data baserow/baserow:1.13.3 \
|
||||
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.13.2 backend-cmd-with-db backup -f /baserow/host/backup.tar.gz
|
||||
baserow/baserow:1.13.3 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.13.2
|
||||
baserow/baserow:1.13.3
|
||||
```
|
||||
|
||||
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.13.2
|
||||
FROM baserow/baserow:1.13.3
|
||||
|
||||
# Any .sh files found in /baserow/supervisor/env/ will be sourced and loaded at startup
|
||||
# useful for storing your own environment variable overrides.
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@ cat << EOF
|
|||
██████╔╝██║ ██║███████║███████╗██║ ██║╚██████╔╝╚███╔███╔╝
|
||||
╚═════╝ ╚═╝ ╚═╝╚══════╝╚══════╝╚═╝ ╚═╝ ╚═════╝ ╚══╝╚══╝
|
||||
|
||||
Version 1.13.2
|
||||
Version 1.13.3
|
||||
|
||||
=========================================================================================
|
||||
EOF
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@
|
|||
"contactEmail": "bram@baserow.io",
|
||||
"icon": "file://logo.png",
|
||||
"tags": ["no-code", "nocode", "database", "data", "collaborate", "airtable"],
|
||||
"version": "1.13.2",
|
||||
"version": "1.13.3",
|
||||
"healthCheckPath": "/api/_health/",
|
||||
"httpPort": 80,
|
||||
"addons": {
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
ARG FROM_IMAGE=baserow/baserow:1.13.2
|
||||
ARG FROM_IMAGE=baserow/baserow:1.13.3
|
||||
# This is pinned as version pinning is done by the CI setting FROM_IMAGE.
|
||||
# hadolint ignore=DL3006
|
||||
FROM $FROM_IMAGE as image_base
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
ARG FROM_IMAGE=baserow/baserow:1.13.2
|
||||
ARG FROM_IMAGE=baserow/baserow:1.13.3
|
||||
# This is pinned as version pinning is done by the CI setting FROM_IMAGE.
|
||||
# hadolint ignore=DL3006
|
||||
FROM $FROM_IMAGE as image_base
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ version: "3.4"
|
|||
services:
|
||||
baserow:
|
||||
container_name: baserow
|
||||
image: baserow/baserow:1.13.2
|
||||
image: baserow/baserow:1.13.3
|
||||
environment:
|
||||
BASEROW_PUBLIC_URL: 'http://localhost'
|
||||
ports:
|
||||
|
|
|
|||
|
|
@ -129,7 +129,7 @@ x-backend-variables: &backend-variables
|
|||
|
||||
services:
|
||||
backend:
|
||||
image: baserow/backend:1.13.2
|
||||
image: baserow/backend:1.13.3
|
||||
restart: unless-stopped
|
||||
ports:
|
||||
- "${HOST_PUBLISH_IP:-127.0.0.1}:8000:8000"
|
||||
|
|
@ -144,7 +144,7 @@ services:
|
|||
local:
|
||||
|
||||
web-frontend:
|
||||
image: baserow/web-frontend:1.13.2
|
||||
image: baserow/web-frontend:1.13.3
|
||||
restart: unless-stopped
|
||||
ports:
|
||||
- "${HOST_PUBLISH_IP:-127.0.0.1}:3000:3000"
|
||||
|
|
@ -169,7 +169,7 @@ services:
|
|||
local:
|
||||
|
||||
celery:
|
||||
image: baserow/backend:1.13.2
|
||||
image: baserow/backend:1.13.3
|
||||
restart: unless-stopped
|
||||
environment:
|
||||
<<: *backend-variables
|
||||
|
|
@ -186,7 +186,7 @@ services:
|
|||
local:
|
||||
|
||||
celery-export-worker:
|
||||
image: baserow/backend:1.13.2
|
||||
image: baserow/backend:1.13.3
|
||||
restart: unless-stopped
|
||||
command: celery-exportworker
|
||||
environment:
|
||||
|
|
@ -203,7 +203,7 @@ services:
|
|||
local:
|
||||
|
||||
celery-beat-worker:
|
||||
image: baserow/backend:1.13.2
|
||||
image: baserow/backend:1.13.3
|
||||
restart: unless-stopped
|
||||
command: celery-beat
|
||||
environment:
|
||||
|
|
|
|||
|
|
@ -155,7 +155,7 @@ services:
|
|||
local:
|
||||
|
||||
backend:
|
||||
image: baserow/backend:1.13.2
|
||||
image: baserow/backend:1.13.3
|
||||
restart: unless-stopped
|
||||
environment:
|
||||
<<: *backend-variables
|
||||
|
|
@ -168,7 +168,7 @@ services:
|
|||
local:
|
||||
|
||||
web-frontend:
|
||||
image: baserow/web-frontend:1.13.2
|
||||
image: baserow/web-frontend:1.13.3
|
||||
restart: unless-stopped
|
||||
environment:
|
||||
BASEROW_PUBLIC_URL: ${BASEROW_PUBLIC_URL-http://localhost}
|
||||
|
|
@ -191,7 +191,7 @@ services:
|
|||
local:
|
||||
|
||||
celery:
|
||||
image: baserow/backend:1.13.2
|
||||
image: baserow/backend:1.13.3
|
||||
restart: unless-stopped
|
||||
environment:
|
||||
<<: *backend-variables
|
||||
|
|
@ -208,7 +208,7 @@ services:
|
|||
local:
|
||||
|
||||
celery-export-worker:
|
||||
image: baserow/backend:1.13.2
|
||||
image: baserow/backend:1.13.3
|
||||
restart: unless-stopped
|
||||
command: celery-exportworker
|
||||
environment:
|
||||
|
|
@ -225,7 +225,7 @@ services:
|
|||
local:
|
||||
|
||||
celery-beat-worker:
|
||||
image: baserow/backend:1.13.2
|
||||
image: baserow/backend:1.13.3
|
||||
restart: unless-stopped
|
||||
command: celery-beat
|
||||
environment:
|
||||
|
|
|
|||
|
|
@ -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.13.2` image or the example
|
||||
We strongly recommend you use our `baserow/baserow:1.13.3` image or the example
|
||||
`docker-compose.yml` files (excluding the `.no-caddy.yml` variant) provided in
|
||||
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
|
||||
> make sure you are using one of the two following deployment methods:
|
||||
>
|
||||
> * Your own container setup with our single service `baserow/backend:1.13.2`
|
||||
and `baserow/web-frontend:1.13.2` images.
|
||||
> * Your own container setup with our single service `baserow/backend:1.13.3`
|
||||
and `baserow/web-frontend:1.13.3` images.
|
||||
> * 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.
|
||||
|
|
@ -32,7 +32,7 @@ simplifies your life by:
|
|||
|
||||
Follow this option if you are using:
|
||||
|
||||
* The all-in-one Baserow image `baserow/baserow:1.13.2`
|
||||
* The all-in-one Baserow image `baserow/baserow:1.13.3`
|
||||
* 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.13.2` and `baserow/web-frontend:1.13.2` images with
|
||||
* Our standalone `baserow/backend:1.13.3` and `baserow/web-frontend:1.13.3` 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.13.2` image then you can do this by adding
|
||||
If you are using the `baserow/backend:1.13.3` 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.
|
||||
|
||||
|
|
|
|||
|
|
@ -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.13.2` image or the example
|
||||
We strongly recommend you use our `baserow/baserow:1.13.3` image or the example
|
||||
`docker-compose.yml` files (excluding the `.no-caddy.yml` variant) provided in
|
||||
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
|
||||
> make sure you are using one of the two following deployment methods:
|
||||
>
|
||||
> * Your own container setup with our single service `baserow/backend:1.13.2`
|
||||
and `baserow/web-frontend:1.13.2` images.
|
||||
> * Your own container setup with our single service `baserow/backend:1.13.3`
|
||||
and `baserow/web-frontend:1.13.3` images.
|
||||
> * 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.
|
||||
|
|
@ -32,7 +32,7 @@ simplifies your life by:
|
|||
|
||||
Follow this option if you are using:
|
||||
|
||||
* The all-in-one Baserow image `baserow/baserow:1.13.2`
|
||||
* The all-in-one Baserow image `baserow/baserow:1.13.3`
|
||||
* 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.13.2` and `baserow/web-frontend:1.13.2` images with
|
||||
* Our standalone `baserow/backend:1.13.3` and `baserow/web-frontend:1.13.3` 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.13.2` image then you can do this by adding
|
||||
If you are using the `baserow/backend:1.13.3` 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.
|
||||
|
||||
|
|
|
|||
|
|
@ -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.13.2
|
||||
$ cloudron install -l baserow.{YOUR_DOMAIN} --image baserow/cloudron:1.13.3
|
||||
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.13.2
|
||||
cloudron update --app {YOUR_APP_ID} --image baserow/cloudron:1.13.3
|
||||
```
|
||||
|
||||
> Note that you must replace the image with the most recent image of Baserow. The
|
||||
|
|
|
|||
|
|
@ -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.13.2
|
||||
baserow/baserow:1.13.3
|
||||
# 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.13.2
|
||||
baserow/baserow:1.13.3
|
||||
# Check the logs and wait for Baserow to become available
|
||||
docker logs baserow
|
||||
```
|
||||
|
|
|
|||
|
|
@ -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.13.2` which by default starts the Gunicorn Django backend server
|
||||
* `baserow/backend:1.13.3` 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.13.2` which is a Nuxt server providing Server Side rendering
|
||||
* `baserow/web-frontend:1.13.3` 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.13.2` (default command is `gunicorn`)
|
||||
* `baserow/backend:1.13.2` with command `celery-worker`
|
||||
* `baserow/backend:1.13.2` with command `celery-export-worker`
|
||||
* `baserow/web-frontend:1.13.2` (default command is `nuxt-local`)
|
||||
* `baserow/backend:1.13.3` (default command is `gunicorn`)
|
||||
* `baserow/backend:1.13.3` with command `celery-worker`
|
||||
* `baserow/backend:1.13.3` with command `celery-export-worker`
|
||||
* `baserow/web-frontend:1.13.3` (default command is `nuxt-local`)
|
||||
* A postgres database
|
||||
* A redis server
|
||||
|
||||
|
|
|
|||
|
|
@ -16,7 +16,7 @@ version: "3.4"
|
|||
services:
|
||||
baserow:
|
||||
container_name: baserow
|
||||
image: baserow/baserow:1.13.2
|
||||
image: baserow/baserow:1.13.3
|
||||
environment:
|
||||
BASEROW_PUBLIC_URL: 'http://localhost'
|
||||
ports:
|
||||
|
|
|
|||
|
|
@ -27,7 +27,7 @@ docker run \
|
|||
-p 80:80 \
|
||||
-p 443:443 \
|
||||
--restart unless-stopped \
|
||||
baserow/baserow:1.13.2
|
||||
baserow/baserow:1.13.3
|
||||
```
|
||||
|
||||
* 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.13.2` image by default runs all of Baserow's various services in a
|
||||
The `baserow/baserow:1.13.3` 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
|
||||
|
|
@ -143,7 +143,7 @@ docker run \
|
|||
-p 80:80 \
|
||||
-p 443:443 \
|
||||
--restart unless-stopped \
|
||||
baserow/baserow:1.13.2
|
||||
baserow/baserow:1.13.3
|
||||
```
|
||||
|
||||
### Behind a reverse proxy already handling ssl
|
||||
|
|
@ -156,7 +156,7 @@ docker run \
|
|||
-v baserow_data:/baserow/data \
|
||||
-p 80:80 \
|
||||
--restart unless-stopped \
|
||||
baserow/baserow:1.13.2
|
||||
baserow/baserow:1.13.3
|
||||
```
|
||||
|
||||
### On a nonstandard HTTP port
|
||||
|
|
@ -169,7 +169,7 @@ docker run \
|
|||
-v baserow_data:/baserow/data \
|
||||
-p 3001:80 \
|
||||
--restart unless-stopped \
|
||||
baserow/baserow:1.13.2
|
||||
baserow/baserow:1.13.3
|
||||
```
|
||||
|
||||
### With an external PostgresSQL server
|
||||
|
|
@ -188,7 +188,7 @@ docker run \
|
|||
-p 80:80 \
|
||||
-p 443:443 \
|
||||
--restart unless-stopped \
|
||||
baserow/baserow:1.13.2
|
||||
baserow/baserow:1.13.3
|
||||
```
|
||||
|
||||
### With an external Redis server
|
||||
|
|
@ -207,7 +207,7 @@ docker run \
|
|||
-p 80:80 \
|
||||
-p 443:443 \
|
||||
--restart unless-stopped \
|
||||
baserow/baserow:1.13.2
|
||||
baserow/baserow:1.13.3
|
||||
```
|
||||
|
||||
### With an external email server
|
||||
|
|
@ -227,7 +227,7 @@ docker run \
|
|||
-p 80:80 \
|
||||
-p 443:443 \
|
||||
--restart unless-stopped \
|
||||
baserow/baserow:1.13.2
|
||||
baserow/baserow:1.13.3
|
||||
```
|
||||
|
||||
### 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 \
|
||||
-p 80:80 \
|
||||
-p 443:443 \
|
||||
baserow/baserow:1.13.2
|
||||
baserow/baserow:1.13.3
|
||||
```
|
||||
|
||||
### Supply secrets using files
|
||||
|
|
@ -292,7 +292,7 @@ docker run \
|
|||
-v baserow_data:/baserow/data \
|
||||
-p 80:80 \
|
||||
-p 443:443 \
|
||||
baserow/baserow:1.13.2
|
||||
baserow/baserow:1.13.3
|
||||
```
|
||||
|
||||
### Start just the embedded database
|
||||
|
|
@ -305,7 +305,7 @@ docker run -it \
|
|||
--name baserow \
|
||||
-p 5432:5432 \
|
||||
-v baserow_data:/baserow/data \
|
||||
baserow/baserow:1.13.2 \
|
||||
baserow/baserow:1.13.3 \
|
||||
start-only-db
|
||||
# Now get the password from
|
||||
docker exec -it baserow cat /baserow/data/.pgpass
|
||||
|
|
@ -323,7 +323,7 @@ docker run -it \
|
|||
--rm \
|
||||
--name baserow \
|
||||
-v baserow_data:/baserow/data \
|
||||
baserow/baserow:1.13.2 \
|
||||
baserow/baserow:1.13.3 \
|
||||
backend-cmd-with-db manage dbshell
|
||||
```
|
||||
|
||||
|
|
@ -381,16 +381,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.13.2 \
|
||||
docker run -it --rm -v baserow_data:/baserow/data baserow/baserow:1.13.3 \
|
||||
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.13.2 \
|
||||
docker run -it --rm -v baserow_data:/baserow/data baserow/baserow:1.13.3 \
|
||||
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.13.2 backend-cmd-with-db backup -f /baserow/host/backup.tar.gz
|
||||
baserow/baserow:1.13.3 backend-cmd-with-db backup -f /baserow/host/backup.tar.gz
|
||||
```
|
||||
|
||||
### Restore only Baserow's Postgres Database
|
||||
|
|
@ -459,7 +459,7 @@ docker run \
|
|||
-p 80:80 \
|
||||
-p 443:443 \
|
||||
--restart unless-stopped \
|
||||
baserow/baserow:1.13.2
|
||||
baserow/baserow:1.13.3
|
||||
```
|
||||
|
||||
Or you can just store it directly in the volume at `baserow_data/env` meaning it will be
|
||||
|
|
@ -468,7 +468,7 @@ loaded whenever you mount in this data volume.
|
|||
### Building your own image from Baserow
|
||||
|
||||
```dockerfile
|
||||
FROM baserow/baserow:1.13.2
|
||||
FROM baserow/baserow:1.13.3
|
||||
|
||||
# Any .sh files found in /baserow/supervisor/env/ will be sourced and loaded at startup
|
||||
# useful for storing your own environment variable overrides.
|
||||
|
|
|
|||
|
|
@ -161,7 +161,7 @@ spec:
|
|||
topologyKey: "kubernetes.io/hostname"
|
||||
containers:
|
||||
- name: backend-asgi
|
||||
image: baserow/backend:1.13.2
|
||||
image: baserow/backend:1.13.3
|
||||
workingDir: /baserow
|
||||
args:
|
||||
- "gunicorn"
|
||||
|
|
@ -218,7 +218,7 @@ spec:
|
|||
topologyKey: "kubernetes.io/hostname"
|
||||
containers:
|
||||
- name: backend-wsgi
|
||||
image: baserow/backend:1.13.2
|
||||
image: baserow/backend:1.13.3
|
||||
workingDir: /baserow
|
||||
args:
|
||||
- "gunicorn-wsgi"
|
||||
|
|
@ -277,7 +277,7 @@ spec:
|
|||
topologyKey: "kubernetes.io/hostname"
|
||||
containers:
|
||||
- name: backend-worker
|
||||
image: baserow/backend:1.13.2
|
||||
image: baserow/backend:1.13.3
|
||||
args:
|
||||
- "celery-worker"
|
||||
imagePullPolicy: Always
|
||||
|
|
@ -294,7 +294,7 @@ spec:
|
|||
- secretRef:
|
||||
name: YOUR_ENV_SECRET_REF
|
||||
- name: backend-export-worker
|
||||
image: baserow/backend:1.13.2
|
||||
image: baserow/backend:1.13.3
|
||||
args:
|
||||
- "celery-exportworker"
|
||||
imagePullPolicy: Always
|
||||
|
|
@ -311,7 +311,7 @@ spec:
|
|||
- secretRef:
|
||||
name: YOUR_ENV_SECRET_REF
|
||||
- name: backend-beat-worker
|
||||
image: baserow/backend:1.13.2
|
||||
image: baserow/backend:1.13.3
|
||||
args:
|
||||
- "celery-beat"
|
||||
imagePullPolicy: Always
|
||||
|
|
@ -352,7 +352,7 @@ spec:
|
|||
topologyKey: "kubernetes.io/hostname"
|
||||
containers:
|
||||
- name: web-frontend
|
||||
image: baserow/web-frontend:1.13.2
|
||||
image: baserow/web-frontend:1.13.3
|
||||
args:
|
||||
- nuxt
|
||||
ports:
|
||||
|
|
|
|||
|
|
@ -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.13.2
|
||||
image: baserow/baserow:1.13.3
|
||||
container_name: baserow
|
||||
labels:
|
||||
# Explicitly tell Traefik to expose this container
|
||||
|
|
|
|||
|
|
@ -122,7 +122,7 @@ containing metadata about your plugin. It should have the following JSON structu
|
|||
{
|
||||
"name": "TODO",
|
||||
"version": "TODO",
|
||||
"supported_baserow_versions": "1.13.2",
|
||||
"supported_baserow_versions": "1.13.3",
|
||||
"plugin_api_version": "0.0.1-alpha",
|
||||
"description": "TODO",
|
||||
"author": "TODO",
|
||||
|
|
|
|||
|
|
@ -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.13.2
|
||||
FROM baserow/baserow:1.13.3
|
||||
|
||||
# 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.13.2 .`
|
||||
`docker build -t my-customized-baserow:1.13.3 .`
|
||||
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.13.2`
|
||||
`docker run -p 80:80 -v baserow_data:/baserow/data my-customized-baserow:1.13.3`
|
||||
|
||||
### 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.13.2
|
||||
baserow:1.13.3
|
||||
```
|
||||
|
||||
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.13.2` image which does not
|
||||
it, the new container is created from the `baserow/baserow:1.13.3` 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.13.2` and `baserow/web-frontend:1.13.2` images
|
||||
Baserow also provides `baserow/backend:1.13.3` and `baserow/web-frontend:1.13.3` 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.13.2 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.13.2
|
||||
docker run --rm baserow/backend:1.13.3 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.13.3
|
||||
```
|
||||
|
||||
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.13.2 uninstall-plugin plugin_name`
|
||||
3. `docker run --rm -v baserow_data:/baserow/data baserow:1.13.3 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.13.2 .`
|
||||
6. Rebuild your image - `docker build -t my-customized-baserow:1.13.3 .`
|
||||
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.13.2`
|
||||
- `docker run -p 80:80 -v baserow_data:/baserow/data my-customized-baserow:1.13.3`
|
||||
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.13.2 uninstall-plugin plugin_name`
|
||||
2. `docker run --rm -v baserow_data:/baserow/data baserow:1.13.3 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.13.2 list-plugins
|
||||
baserow:1.13.3 list-plugins
|
||||
|
||||
# or on a running container
|
||||
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
ARG FROM_IMAGE=baserow/baserow:1.13.2
|
||||
ARG FROM_IMAGE=baserow/baserow:1.13.3
|
||||
# This is pinned as version pinning is done by the CI setting FROM_IMAGE.
|
||||
# hadolint ignore=DL3006
|
||||
FROM $FROM_IMAGE as image_base
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
FROM baserow/baserow:1.13.2
|
||||
FROM baserow/baserow:1.13.3
|
||||
|
||||
COPY ./plugins/{{ cookiecutter.project_module }}/ /baserow/plugins/{{ cookiecutter.project_module }}/
|
||||
RUN /baserow/plugins/install_plugin.sh --folder /baserow/plugins/{{ cookiecutter.project_module }}
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
# This a dev image for testing your plugin when installed into the Baserow backend image
|
||||
FROM baserow/backend:1.13.2 as base
|
||||
FROM baserow/backend:1.13.3 as base
|
||||
|
||||
FROM baserow/backend:1.13.2
|
||||
FROM baserow/backend:1.13.3
|
||||
|
||||
USER root
|
||||
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
FROM baserow/backend:1.13.2
|
||||
FROM baserow/backend:1.13.3
|
||||
|
||||
USER root
|
||||
|
||||
|
|
|
|||
|
|
@ -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.13.2 as base
|
||||
FROM baserow/baserow:1.13.3 as base
|
||||
|
||||
FROM baserow/baserow:1.13.2
|
||||
FROM baserow/baserow:1.13.3
|
||||
|
||||
ARG PLUGIN_BUILD_UID
|
||||
ENV PLUGIN_BUILD_UID=${PLUGIN_BUILD_UID:-9999}
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
{
|
||||
"name": "{{ cookiecutter.project_name }}",
|
||||
"version": "0.0.1",
|
||||
"supported_baserow_versions": "1.13.2",
|
||||
"supported_baserow_versions": "1.13.3",
|
||||
"plugin_api_version": "0.0.1-alpha",
|
||||
"description": "TODO",
|
||||
"author": "TODO",
|
||||
|
|
|
|||
|
|
@ -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.13.2 as base
|
||||
FROM baserow/web-frontend:1.13.2
|
||||
FROM baserow/web-frontend:1.13.3 as base
|
||||
FROM baserow/web-frontend:1.13.3
|
||||
|
||||
USER root
|
||||
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
FROM baserow/web-frontend:1.13.2
|
||||
FROM baserow/web-frontend:1.13.3
|
||||
|
||||
USER root
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
{
|
||||
"name": "baserow",
|
||||
"version": "1.13.2",
|
||||
"version": "1.13.3",
|
||||
"private": true,
|
||||
"description": "Baserow: open source no-code database web frontend.",
|
||||
"author": "Bram Wiepjes (Baserow)",
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue