Compare commits

...
4 Commits
Author SHA1 Message Date
fauno 545720fe9b feat: s3
continuous-integration/drone/pr Build is failing
2026-10-28 15:25:03 -03:00
fauno 1378ef4330 Merge pull request 'adds maintenance and updates readme' (#31) from LIT_as_maintainers into main
continuous-integration/drone/push Build is failing
Reviewed-on: #31
Reviewed-by: fauno <fauno@sutty.coop.ar>
2026-08-26 17:53:53 +00:00
carla 018097c4d2 adds fauno and updates renovate with reviewers
continuous-integration/drone/pr Build is failing
2026-08-26 15:22:37 +02:00
carla 3a8164d3a1 adds maintenance and updates readme
continuous-integration/drone/pr Build is failing
2026-08-26 13:19:22 +02:00
7 changed files with 64 additions and 3 deletions
+9
View File
@@ -57,3 +57,12 @@ COMPOSE_FILE="compose.yml"
# Only present in config.json (no equivalent env var):
# DOCUMENT_MAX_LENGTH=100000
# CMD_ENABLE_UPLOADS=registered
# S3 uploads
#COMPOSE_FILE="$COMPOSE_FILE:compose.s3.yml"
#CMD_S3_ACCESS_KEY_ID=
#CMD_S3_REGION=garage
#CMD_S3_BUCKET=$DOMAIN
#CMD_S3_ENDPOINT=
#CMD_S3_FOLDER=uploads
#SECRET_S3_SECRET_ACCESS_KEY_VERSION=v1
+32
View File
@@ -0,0 +1,32 @@
# Hedgedoc 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 week
- Make image major updates every three months
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 [hedgedoc maintainers team](https://git.coopcloud.tech/org/coop-cloud/teams/hedgedoc-maintainers).
4. Join the room [#cc-|-hedgedoc-maintenance:matrix.org](#cc-|-hedgedoc-maintenance:matrix.org) and chat to other maintainers.
+2 -1
View File
@@ -5,8 +5,9 @@
[Hedgedoc][hedegedoc] using Coöp Cloud ♥
<!-- metadata -->
* **Maintainer**: [@fauno](https://git.coopcloud.tech/fauno) , Local-IT: [@moritz](https://git.coopcloud.tech/moritz), [@msimon](https://git.coopcloud.tech/simon), [@carla](https://git.coopcloud.tech/carla)
* **Category**: Apps
* **Status**: 2, beta
* **Status**: 3
* **Image**: [`quay.io/hedgedoc/hedgedoc`](https://quay.io/hedgedoc/hedgedoc), 4, upstream
* **Healthcheck**: Yes
* **Backups**: Yes
+1 -1
View File
@@ -1,3 +1,3 @@
export ENTRYPOINT_CONF_VERSION=v13
export ENTRYPOINT_CONF_VERSION=v14
export CONFIG_JSON_VERSION=v1
export PG_BACKUP_VERSION=v1
+17
View File
@@ -0,0 +1,17 @@
---
version: "3.8"
services:
app:
environment:
- CMD_S3_ACCESS_KEY_ID
- CMD_S3_REGION
- CMD_S3_BUCKET
- CMD_S3_ENDPOINT
- CMD_S3_FOLDER
- CMD_S3_PUBLIC_FILES=false
secrets:
- s3_secret_access_key
secrets:
s3_secret_access_key:
external: true
name: ${STACK_NAME}_s3_secret_access_key_${SECRET_S3_SECRET_ACCESS_KEY_VERSION}
+1
View File
@@ -27,6 +27,7 @@ load_vars() {
fi
file_env "CMD_OAUTH2_CLIENT_SECRET"
file_env "CMD_SESSION_SECRET"
file_env "CMD_S3_SECRET_ACCESS_KEY"
}
main() {
+2 -1
View File
@@ -2,5 +2,6 @@
"$schema": "https://docs.renovatebot.com/renovate-schema.json",
"extends": [
"config:base"
]
],
"reviewers": ["fauno","moritz","simon","carla"]
}