From 6a0711aba7dc5ffdf6b3d54de7b1cb59bf6d499e Mon Sep 17 00:00:00 2001 From: silk Date: Tue, 24 Mar 2026 18:41:51 +0000 Subject: [PATCH 1/2] Initial commit --- README.md | 93 +++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 93 insertions(+) create mode 100644 README.md diff --git a/README.md b/README.md new file mode 100644 index 0000000..72faee3 --- /dev/null +++ b/README.md @@ -0,0 +1,93 @@ +# baserow + + + +## Getting started + +To make it easy for you to get started with GitLab, here's a list of recommended next steps. + +Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)! + +## Add your files + +- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files +- [ ] [Add files using the command line](https://docs.gitlab.com/topics/git/add_files/#add-files-to-a-git-repository) or push an existing Git repository with the following command: + +``` +cd existing_repo +git remote add origin https://git.mirnet.org/mir/coop-cloud-recipes/baserow.git +git branch -M main +git push -uf origin main +``` + +## Integrate with your tools + +- [ ] [Set up project integrations](https://git.mirnet.org/mir/coop-cloud-recipes/baserow/-/settings/integrations) + +## Collaborate with your team + +- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/) +- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html) +- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically) +- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/) +- [ ] [Set auto-merge](https://docs.gitlab.com/user/project/merge_requests/auto_merge/) + +## Test and Deploy + +Use the built-in continuous integration in GitLab. + +- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/) +- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)](https://docs.gitlab.com/ee/user/application_security/sast/) +- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html) +- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/) +- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html) + +*** + +# Editing this README + +When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to [makeareadme.com](https://www.makeareadme.com/) for this template. + +## Suggestions for a good README + +Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information. + +## Name +Choose a self-explaining name for your project. + +## Description +Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors. + +## Badges +On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge. + +## Visuals +Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method. + +## Installation +Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection. + +## Usage +Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README. + +## Support +Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc. + +## Roadmap +If you have ideas for releases in the future, it is a good idea to list them in the README. + +## Contributing +State if you are open to contributions and what your requirements are for accepting them. + +For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self. + +You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser. + +## Authors and acknowledgment +Show your appreciation to those who have contributed to the project. + +## License +For open source projects, say how it is licensed. + +## Project status +If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers. From e9e606a33a9e0f20e99e76dc339416eeee16fde8 Mon Sep 17 00:00:00 2001 From: silk Date: Tue, 24 Mar 2026 18:47:15 +0000 Subject: [PATCH 2/2] Baserow with license fix --- .drone.yml | 38 ++++++++++++++++ .env.sample | 32 +++++++++++++ .gitignore | 1 + README.md | 106 +++++++++++-------------------------------- abra.sh | 3 ++ backup-postgres.sh | 22 +++++++++ compose.email.yml | 21 +++++++++ compose.license.yml | 23 ++++++++++ compose.yml | 68 +++++++++++++++++++++++++++ entrypoint.sh.tmpl | 7 +++ license-fix.patch | 82 +++++++++++++++++++++++++++++++++ release/0.2.0+1.21.2 | 1 + release/0.3.0+1.25.2 | 1 + release/1.0.0+1.31.1 | 7 +++ release/1.3.0+1.35.3 | 1 + release/2.0.0+2.0.5 | 3 ++ 16 files changed, 336 insertions(+), 80 deletions(-) create mode 100644 .drone.yml create mode 100644 .env.sample create mode 100644 .gitignore create mode 100644 abra.sh create mode 100644 backup-postgres.sh create mode 100644 compose.email.yml create mode 100644 compose.license.yml create mode 100644 compose.yml create mode 100644 entrypoint.sh.tmpl create mode 100644 license-fix.patch create mode 100644 release/0.2.0+1.21.2 create mode 100644 release/0.3.0+1.25.2 create mode 100644 release/1.0.0+1.31.1 create mode 100644 release/1.3.0+1.35.3 create mode 100644 release/2.0.0+2.0.5 diff --git a/.drone.yml b/.drone.yml new file mode 100644 index 0000000..cd906e2 --- /dev/null +++ b/.drone.yml @@ -0,0 +1,38 @@ +--- +kind: pipeline +name: deploy to swarm-test.autonomic.zone +steps: + - name: deployment + image: git.coopcloud.tech/coop-cloud/stack-ssh-deploy:latest + settings: + host: swarm-test.autonomic.zone + stack: baserow + generate_secrets: true + purge: true + deploy_key: + from_secret: drone_ssh_swarm_test + networks: + - proxy + environment: + DOMAIN: baserow.swarm-test.autonomic.zone + STACK_NAME: baserow + LETS_ENCRYPT_ENV: production +trigger: + branch: + - main +--- +kind: pipeline +name: generate recipe catalogue +steps: + - name: release a new version + image: plugins/downstream + settings: + server: https://build.coopcloud.tech + token: + from_secret: drone_abra-bot_token + fork: true + repositories: + - toolshed/auto-recipes-catalogue-json + +trigger: + event: tag diff --git a/.env.sample b/.env.sample new file mode 100644 index 0000000..cbbb9eb --- /dev/null +++ b/.env.sample @@ -0,0 +1,32 @@ +TYPE=baserow + +DOMAIN=baserow.example.com + +COMPOSE_FILE="compose.yml" + +## Domain aliases +#EXTRA_DOMAINS=', `www.baserow.example.com`' + +## Automatically use subdomains under following domain (anything.example.com) +#WILDCARD_DOMAIN='example.com' + +LETS_ENCRYPT_ENV=production + +## For low-resource machines (<2GB ram) +# BASEROW_AMOUNT_OF_GUNICORN_WORKERS=1 +# BASEROW_AMOUNT_OF_WORKERS=1 +# BASEROW_RUN_MINIMAL=yes + +# COMPOSE_FILE="$COMPOSE_FILE:compose.email.yml" +# FROM_EMAIL="No Reply " +# EMAIL_SMTP_USE_TLS=true +# EMAIL_SMTP_HOST=mail.exampl.com +# EMAIL_SMTP_PORT=497 +# EMAIL_SMTP_USER=noreply@example.com +# SECRET_EMAIL_SMTP_PASSWORD_VERSION=v1 +# + +SECRET_SECRET_KEY_VERSION=v1 +SECRET_JWT_KEY_VERSION=v1 + +# COMPOSE_FILE="$COMPOSE_FILE:compose.license.yml" \ No newline at end of file diff --git a/.gitignore b/.gitignore new file mode 100644 index 0000000..7a6353d --- /dev/null +++ b/.gitignore @@ -0,0 +1 @@ +.envrc diff --git a/README.md b/README.md index 72faee3..c918fe5 100644 --- a/README.md +++ b/README.md @@ -1,93 +1,39 @@ # baserow +> Minimum Viable deploy of Baserow: Open source no-code database and Airtable alternative + -## Getting started +* **Category**: Apps +* **Status**: 0 +* **Image**: [`baserow`](https://hub.docker.com/r/baserow), 4, upstream +* **Healthcheck**: Yes (using https://baserow.io/docs/installation%2Finstall-with-docker#running-healthchecks-on-baserow) +* **Backups**: No +* **Email**: No +* **Tests**: No +* **SSO**: No -To make it easy for you to get started with GitLab, here's a list of recommended next steps. + -Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)! +## Quick start -## Add your files +* `abra app new baserow` +* `abra app config ` +* `abra app deploy ` -- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files -- [ ] [Add files using the command line](https://docs.gitlab.com/topics/git/add_files/#add-files-to-a-git-repository) or push an existing Git repository with the following command: +## Resources -``` -cd existing_repo -git remote add origin https://git.mirnet.org/mir/coop-cloud-recipes/baserow.git -git branch -M main -git push -uf origin main -``` +* Baserow requires over 2GB RAM to run on Co-op Cloud with default settings +* For environments with 2GB or less RAM, run `abra app config ` and uncomment the `For low-resource machines` config block +* More info: https://hub.docker.com/r/baserow/baserow/#scaling-options -## Integrate with your tools +## Baserow Crack -- [ ] [Set up project integrations](https://git.mirnet.org/mir/coop-cloud-recipes/baserow/-/settings/integrations) +* `abra app config `. Uncomment the final line of the config `# COMPOSE_FILE="$COMPOSE_FILE:compose.license.yml"` +* `abra app undeploy ` +* `abra app deploy ` +* Navigate to the admin panel -> manage licenses. Click Register License and type in any string. An enterprise without support license should be given. +* Refresh the page to access features! -## Collaborate with your team +For more, see [`docs.coopcloud.tech`](https://docs.coopcloud.tech). -- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/) -- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html) -- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically) -- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/) -- [ ] [Set auto-merge](https://docs.gitlab.com/user/project/merge_requests/auto_merge/) - -## Test and Deploy - -Use the built-in continuous integration in GitLab. - -- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/) -- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)](https://docs.gitlab.com/ee/user/application_security/sast/) -- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html) -- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/) -- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html) - -*** - -# Editing this README - -When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to [makeareadme.com](https://www.makeareadme.com/) for this template. - -## Suggestions for a good README - -Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information. - -## Name -Choose a self-explaining name for your project. - -## Description -Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors. - -## Badges -On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge. - -## Visuals -Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method. - -## Installation -Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection. - -## Usage -Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README. - -## Support -Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc. - -## Roadmap -If you have ideas for releases in the future, it is a good idea to list them in the README. - -## Contributing -State if you are open to contributions and what your requirements are for accepting them. - -For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self. - -You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser. - -## Authors and acknowledgment -Show your appreciation to those who have contributed to the project. - -## License -For open source projects, say how it is licensed. - -## Project status -If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers. diff --git a/abra.sh b/abra.sh new file mode 100644 index 0000000..7bcfe9c --- /dev/null +++ b/abra.sh @@ -0,0 +1,3 @@ +export PG_BACKUP_CONFIG_VERSION=v1 +export ENTRYPOINT_VERSION=v1 +export LICENSE_FIX_VERSION=v1 \ No newline at end of file diff --git a/backup-postgres.sh b/backup-postgres.sh new file mode 100644 index 0000000..7c4bad0 --- /dev/null +++ b/backup-postgres.sh @@ -0,0 +1,22 @@ +if [ "$1" == "pre-backup" ]; then + # Remove any existing db dump and then create a new one + rm -rf $DATA_DIR/postgres/postgres-backup + source /baserow/data/.pgpass + PGPASSWORD=$DATABASE_PASSWORD pg_dump -j 8 -h localhost -U baserow baserow --format=directory -f $DATA_DIR/postgres/postgres-backup + exit +fi + +if [ "$1" == "post-backup" ]; then + rm -rf $DATA_DIR/postgres/postgres-backup + exit +fi + +if [ "$1" == "pre-restore" ]; then + exit +fi + +if [ "$1" == "post-restore" ]; then + source /baserow/data/.pgpass + PGPASSWORD=$DATABASE_PASSWORD pg_restore -j 8 -h localhost -U baserow -d baserow -c $DATA_DIR/postgres/postgres-backup + exit +fi \ No newline at end of file diff --git a/compose.email.yml b/compose.email.yml new file mode 100644 index 0000000..a0fb5ed --- /dev/null +++ b/compose.email.yml @@ -0,0 +1,21 @@ +--- +version: "3.8" + +services: + app: + environment: + - EMAIL_SMTP=true + - EMAIL_SMTP_PASSWORD_FILE=/run/secrets/email_smtp_password + - FROM_EMAIL + - EMAIL_SMTP_USE_TLS + - EMAIL_SMTP_HOST + - EMAIL_SMTP_PORT + - EMAIL_SMTP_USER + secrets: + - email_smtp_password + +secrets: + email_smtp_password: + external: true + name: ${STACK_NAME}_email_smtp_password_${SECRET_EMAIL_SMTP_PASSWORD_VERSION} + diff --git a/compose.license.yml b/compose.license.yml new file mode 100644 index 0000000..a18d37c --- /dev/null +++ b/compose.license.yml @@ -0,0 +1,23 @@ +--- +version: "3.8" + +services: + app: + configs: + - source: entrypoint + target: /entrypoint.sh + mode: 0555 + - source: license_fix + target: /baserow/license-fix.patch + mode: 0644 + entrypoint: + /entrypoint.sh + +configs: + license_fix: + name: ${STACK_NAME}_license_fix_${LICENSE_FIX_VERSION} + file: license-fix.patch + entrypoint: + name: ${STACK_NAME}_entrypoint_${ENTRYPOINT_VERSION} + file: entrypoint.sh.tmpl + template_driver: golang \ No newline at end of file diff --git a/compose.yml b/compose.yml new file mode 100644 index 0000000..3b21ad5 --- /dev/null +++ b/compose.yml @@ -0,0 +1,68 @@ +--- +version: "3.8" + +services: + app: + image: baserow/baserow:2.0.5 + networks: + - proxy + environment: + - BASEROW_PUBLIC_URL=https://${DOMAIN} + - SECRET_KEY_FILE=/run/secrets/secret_key + - BASEROW_JWT_SIGNING_KEY_FILE=/run/secrets/jwt_key + - BASEROW_CADDY_ADDRESSES=:80 + - BASEROW_BUILDER_DOMAINS=${WILDCARD_DOMAIN} + secrets: + - secret_key + - jwt_key + deploy: + restart_policy: + condition: on-failure + labels: + - "traefik.enable=true" + - "traefik.http.services.${STACK_NAME}.loadbalancer.server.port=80" + - "traefik.http.routers.${STACK_NAME}.rule=Host(`${DOMAIN}`${EXTRA_DOMAINS}) || HostRegexp(`{subdomain:\\w+}.${WILDCARD_DOMAIN}`)" + - "traefik.http.routers.${STACK_NAME}.entrypoints=web-secure" + - "traefik.http.routers.${STACK_NAME}.tls.certresolver=${LETS_ENCRYPT_ENV}" + ## Redirect from EXTRA_DOMAINS to DOMAIN + #- "traefik.http.routers.${STACK_NAME}.middlewares=${STACK_NAME}-redirect" + #- "traefik.http.middlewares.${STACK_NAME}-redirect.headers.SSLForceHost=true" + #- "traefik.http.middlewares.${STACK_NAME}-redirect.headers.SSLHost=${DOMAIN}" + - "backupbot.backup=true" + - "backupbot.backup.path=/baserow/data" + - "backupbot.backup.pre-hook=/backup.sh pre-backup" + - "backupbot.backup.post-hook=/backup.sh post-backup" + - "backupbot.restore.post-hook=/backup.sh post-restore" + - "coop-cloud.${STACK_NAME}.version=2.0.0+2.0.5" + healthcheck: + test: ["CMD", "./baserow.sh", "backend-cmd", "backend-healthcheck"] + interval: 30s + timeout: 10s + retries: 10 + start_period: 1m + volumes: + - baserow_data:/baserow/data + configs: + - source: backup-postgres + target: /backup.sh + mode: 0777 + +volumes: + baserow_data: + +configs: + backup-postgres: + name: backup-postgres_${PG_BACKUP_CONFIG_VERSION} + file: ./backup-postgres.sh + +networks: + proxy: + external: true + +secrets: + secret_key: + external: true + name: ${STACK_NAME}_secret_key_${SECRET_SECRET_KEY_VERSION} + jwt_key: + external: true + name: ${STACK_NAME}_jwt_key_${SECRET_JWT_KEY_VERSION} diff --git a/entrypoint.sh.tmpl b/entrypoint.sh.tmpl new file mode 100644 index 0000000..10efb65 --- /dev/null +++ b/entrypoint.sh.tmpl @@ -0,0 +1,7 @@ +#!/bin/bash + +cd baserow +patch -p1 < license-fix.patch +cd .. + +/baserow.sh start "$@" \ No newline at end of file diff --git a/license-fix.patch b/license-fix.patch new file mode 100644 index 0000000..de5ecfb --- /dev/null +++ b/license-fix.patch @@ -0,0 +1,82 @@ +diff --git a/premium/backend/src/baserow_premium/license/handler.py b/premium/backend/src/baserow_premium/license/handler.py +index dea20281e..70448036b 100755 +--- a/premium/backend/src/baserow_premium/license/handler.py ++++ b/premium/backend/src/baserow_premium/license/handler.py +@@ -381,7 +381,7 @@ class LicenseHandler: + :param license_objects: The license objects that must be checked + :return: The updated license objects. + """ +- ++ return license_objects + try: + authority_response = ( + cls.send_license_info_and_fetch_license_status_with_authority( +@@ -474,7 +474,13 @@ class LicenseHandler: + :raises LicenseHasExpiredError: When the license has expired. + :return: The created license instance. + """ +- ++ obj = License( ++ license="", ++ last_check=None, ++ cached_untrusted_instance_wide=True ++ ) ++ obj.save() ++ return obj + if not requesting_user.is_staff: + raise IsNotAdminError() + +diff --git a/premium/backend/src/baserow_premium/license/models.py b/premium/backend/src/baserow_premium/license/models.py +index f0d8d08d9..2184c759d 100644 +--- a/premium/backend/src/baserow_premium/license/models.py ++++ b/premium/backend/src/baserow_premium/license/models.py +@@ -35,7 +35,23 @@ class License(models.Model): + @cached_property + def payload(self): + from .handler import LicenseHandler +- ++ return { ++ "id": 0, ++ "license_id": "", ++ "is_active": True, ++ "last_check": None, ++ "valid_from": "2023-01-01T00:00:00Z", ++ "valid_through": "2100-01-01T00:00:00Z", ++ "free_users_count": 100000, ++ "seats_taken": 0, ++ "seats": 100000, ++ "application_users_taken": 0, ++ "application_users": 0, ++ "product_code": "enterprise_without_support", ++ "issued_on": "2023-01-01T00:00:00Z", ++ "issued_to_name": "", ++ "issued_to_email": "", ++ } + possibly_encoded_license = self.license + if isinstance(possibly_encoded_license, str): + encoded_license = possibly_encoded_license.encode() +@@ -61,7 +77,6 @@ class License(models.Model): + An active license is one which is valid right now and has valid cached + properties which haven't been manipulated. + """ +- + return ( + self.valid_from <= datetime.now(tz=timezone.utc) <= self.valid_through + and self.valid_cached_properties +@@ -87,7 +102,7 @@ class License(models.Model): + decoded properties from the signed license. If they don't match then manual + changes have been made to the cached properties. + """ +- ++ return True + return self.cached_untrusted_instance_wide == self.license_type.instance_wide + + @property +@@ -118,7 +133,6 @@ class License(models.Model): + @property + def license_type(self): + from baserow_premium.license.registries import license_type_registry +- + return license_type_registry.get(self.product_code) + + diff --git a/release/0.2.0+1.21.2 b/release/0.2.0+1.21.2 new file mode 100644 index 0000000..09a825d --- /dev/null +++ b/release/0.2.0+1.21.2 @@ -0,0 +1 @@ +Fix compose file \ No newline at end of file diff --git a/release/0.3.0+1.25.2 b/release/0.3.0+1.25.2 new file mode 100644 index 0000000..036a530 --- /dev/null +++ b/release/0.3.0+1.25.2 @@ -0,0 +1 @@ +WARNING: this version includes a major Postgres upgrade, you need to follow the steps here, ideally BEFORE upgrading: https://baserow.io/docs/installation%2Finstall-with-docker#upgrade-process \ No newline at end of file diff --git a/release/1.0.0+1.31.1 b/release/1.0.0+1.31.1 new file mode 100644 index 0000000..b6ae9cf --- /dev/null +++ b/release/1.0.0+1.31.1 @@ -0,0 +1,7 @@ +This upgrade changes the name of the jwt signing key secret from baserow_jwt_signing_key to jwt_key +EXISTING DEPLOYMENTS MUST COPY THIS SECRET TO THE NEW LOCATION: +# Retrieve the current jwt key value: +docker exec cat /run/secrets/baserow_jwt_signing_key +# Create the new secret +abra app secret insert jwt_key v1 + diff --git a/release/1.3.0+1.35.3 b/release/1.3.0+1.35.3 new file mode 100644 index 0000000..2b7b378 --- /dev/null +++ b/release/1.3.0+1.35.3 @@ -0,0 +1 @@ +Backup/restore of the postgres database backend will now use pg_dump and pg_restore \ No newline at end of file diff --git a/release/2.0.0+2.0.5 b/release/2.0.0+2.0.5 new file mode 100644 index 0000000..ac6cb24 --- /dev/null +++ b/release/2.0.0+2.0.5 @@ -0,0 +1,3 @@ += 1 Breaking Change = + +[Builder] Data source now return content with human property names instead of technical ones #4135 \ No newline at end of file