Compare commits

..

3 Commits

Author SHA1 Message Date
fauno 20c3e6d5d3 chore: publish 1.1.0+0.258.11 release
continuous-integration/drone/tag Build is passing
2025-01-02 17:00:10 -03:00
fauno b471841243 Merge branch 'backups' 2025-01-02 16:57:41 -03:00
fauno 79266d8929 fix: upgrade to 0.258.11 2025-01-02 16:51:53 -03:00
11 changed files with 5 additions and 128 deletions
+1 -1
View File
@@ -34,7 +34,7 @@ steps:
from_secret: drone_abra-bot_token
fork: true
repositories:
- toolshed/auto-recipes-catalogue-json
- coop-cloud/auto-recipes-catalogue-json
trigger:
event: tag
-12
View File
@@ -10,15 +10,3 @@ LETS_ENCRYPT_ENV=production
SECRET_DB_PASSWORD_VERSION=v1
SECRET_NC_DB_URL_VERSION=v1
ENABLE_BACKUPS=true
COMPOSE_FILE="compose.yml"
# ---- UNCOMMENT THESE LINES FOR ENTERPRISE VERSION USE ----
#COMPOSE_FILE="$COMPOSE_FILE:compose.license.yml"
# License to enable enterprise features.
#NC_LICENSE_KEY=<YOUR_LICENSE_HERE>
#JWT used for authentication in enterprise version
#SECRET_AUTH_JWT_VERSION=v1
#NC_AUTH_JWT_SECRET_FILE=/run/secrets/auth_jwt
-32
View File
@@ -1,32 +0,0 @@
# NocoDB Recipe Maintenance
All contributions should be made via a pull request. This is to ensure a
certain quality and consistency, that others can rely on.
## Maintainer Responsibilities
A recipe maintainer has the following responsibilities:
- Respond to pull requests / issues within two weeks
- Make image security updates within a day
- Make image patch / minor updates within a week
- Make image major updates within a month
In order to fullfill these responsibilities a recipe maintainer:
- Has to watch the repository (to get notifications)
- Needs to make sure renovate is configured properly
## Pull Requests
A pull request can be merged if it is approved by at least one maintainer. For
pull requests opened by a maintainer they need to be approved by another
maintainer. Even though it is okay to merge a pull request with one approval, it
is always better if all maintainers looked at the pull request and approved it.
## Become a maintainer
Everyone can apply to be a recipe maintainer:
1. Watch the repository to always get updates
2. Simply add your self to the list in the [README.md](./README.md) and open a new pull request with the change.
3. Once the pull request gets merged you will be added to the [nocodb maintainers team](https://git.coopcloud.tech/org/coop-cloud/teams/nocodb-maintainers).
+1 -9
View File
@@ -4,7 +4,6 @@
<!-- metadata -->
* **Maintainer**: [@fauno](https://git.coopcloud.tech/fauno)
* **Category**: Apps
* **Status**: 0
* **Image**: [`nocodb`](https://hub.docker.com/r/nocodb), 4, upstream
@@ -22,14 +21,7 @@
* `abra app config <app-name>`
* `export DATABASE_PW=$(pwgen 20)`
* `abra app secret insert <app-name> db_password v1 ${DATABASE_PW}`
* `abra app secret insert <app-name> nc_db_url v1 "pg://db:5432?u=nocodb&p=${DATABASE_PW}&d=nocodb"`
* `abra app deploy <app-name>`
## NocoDB Enterprise Version
* `abra app config <app-name>`. Uncomment the variables used for setting enterprise values. Make sure you have a valid license.
* `abra app undeploy <app-name>`
* If `auth_jwt` is ungenerated: `abra app secret generate <app-name> auth_jwt v1`
* `abra app secret insert <app-name> nc_db_url v1 pg://db:5432?u=nocodb&p=${DATABASE_PW}&d=nocodb`
* `abra app deploy <app-name>`
For more, see [`docs.coopcloud.tech`](https://docs.coopcloud.tech).
-1
View File
@@ -1,2 +1 @@
export PG_BACKUP_VERSION=v1
export NOCODB_ENTRYPOINT_VERSION=v1
-25
View File
@@ -1,25 +0,0 @@
version: "3.8"
services:
app:
image: nocodb/nocodb-ee:2026.03.0-pre.01
secrets:
- auth_jwt
configs:
- source: nocodb_entrypoint
target: /entrypoint.sh
mode: 0555
entrypoint: /entrypoint.sh
environment:
NC_LICENSE_KEY: ${NC_LICENSE_KEY}
configs:
nocodb_entrypoint:
name: ${STACK_NAME}_nocodb_entrypoint_${NOCODB_ENTRYPOINT_VERSION}
file: entrypoint.sh.tmpl
template_driver: golang
secrets:
auth_jwt:
external: true
name: ${STACK_NAME}_auth_jwt_${SECRET_AUTH_JWT_VERSION}
+3 -3
View File
@@ -3,7 +3,7 @@ version: "3.8"
services:
app:
image: nocodb/nocodb:2026.04.2
image: nocodb/nocodb:0.258.11
secrets:
- nc_db_url
networks:
@@ -28,8 +28,8 @@ services:
#- "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}"
- "coop-cloud.${STACK_NAME}.version=1.1.0+0.258.11"
- "backupbot.backup=${ENABLE_BACKUPS:-true}"
- "coop-cloud.${STACK_NAME}.version=2.1.6+2026.04.2"
db:
image: postgres:13.2-alpine
@@ -52,7 +52,7 @@ services:
labels:
backupbot.backup: "${ENABLE_BACKUPS:-true}"
backupbot.backup.pre-hook: "/pg_backup.sh backup"
backupbot.backup.volumes.db.path: "backup.sql"
backupbot.backup.volumes.postgres.path: "backup.sql"
backupbot.restore.post-hook: '/pg_backup.sh restore'
configs:
- source: pg_backup
-34
View File
@@ -1,34 +0,0 @@
#!/bin/sh
set -e
echo "Entrypoint running"
file_env() {
var="$1"
fileVar="${var}_FILE"
def="${2:-}"
eval "var_val=\${$var}"
eval "file_val=\${$fileVar}"
if [ -n "$var_val" ] && [ -n "$file_val" ]; then
echo >&2 "error: both $var and $fileVar are set (but are exclusive)"
exit 1
fi
val="$def"
if [ -n "$var_val" ]; then
val="$var_val"
elif [ -n "$file_val" ]; then
val="$(cat "$file_val")"
fi
export "$var=$val"
unset "$fileVar"
}
file_env "NC_AUTH_JWT_SECRET"
echo "Added JWT secret"
/usr/bin/dumb-init -- /usr/src/appEntry/start.sh "$@"
-1
View File
@@ -1 +0,0 @@
Check release notes for license change from AGPL3 to Fair-code: https://github.com/nocodb/nocodb/releases/tag/0.301.0
-1
View File
@@ -1 +0,0 @@
The version numbering changed but the upgrade runs without issues
-9
View File
@@ -1,9 +0,0 @@
{
"$schema": "https://docs.renovatebot.com/renovate-schema.json",
"extends": [
"config:recommended"
],
"reviewers": [
"fauno"
]
}