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
6 changed files with 4 additions and 47 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
-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
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
+3 -3
View File
@@ -3,7 +3,7 @@ version: "3.8"
services:
app:
image: nocodb/nocodb:0.301.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.0+0.301.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
-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
-9
View File
@@ -1,9 +0,0 @@
{
"$schema": "https://docs.renovatebot.com/renovate-schema.json",
"extends": [
"config:recommended"
],
"reviewers": [
"team:nocodb-maintainers"
]
}