Compare commits

...
Author SHA1 Message Date
carla a3082572da adds maintenance and updates readme 2026-08-26 13:19:32 +02:00
simon b10b95b5f6 fix oidc by adding 'offline_access' to oidc scopes
continuous-integration/drone/push Build is failing
2026-08-24 16:46:26 +02:00
3wordchant 00cca6829f docs: Tweak README
continuous-integration/drone/push Build is failing
2026-08-14 14:52:47 -05:00
3wordchant 523eed8344 docs: Yeet more ballast
continuous-integration/drone/push Build is failing
2026-08-13 12:56:31 -05:00
3wordchant eb9856946d docs: Remove ballast README steps 2026-08-13 12:55:51 -05:00
3 changed files with 39 additions and 10 deletions
+1 -1
View File
@@ -76,7 +76,7 @@ ALLOWED_DOMAINS=
#OIDC_USERINFO_URI=
#OIDC_USERNAME_CLAIM=preferred_username
#OIDC_DISPLAY_NAME="My Cool OpenId Connect Provider"
#OIDC_SCOPES="openid profile email"
#OIDC_SCOPES="openid profile email offline_access"
#SECRET_OIDC_CLIENT_SECRET_VERSION=v1
#COMPOSE_FILE="$COMPOSE_FILE:compose.google.yml"
+32
View File
@@ -0,0 +1,32 @@
# Outline 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 [outline maintainers team](https://git.coopcloud.tech/org/coop-cloud/teams/outline-maintainers).
4. Join the room [#cc-|-outline-maintenance:matrix.org](#cc-|-outline-maintenance:matrix.org) and chat to other maintainers.
+6 -9
View File
@@ -3,7 +3,7 @@
Wiki and knowledge base for growing teams
<!-- metadata -->
* **Maintainer**: Local-IT: [@moritz](https://git.coopcloud.tech/moritz), [@msimon](https://git.coopcloud.tech/simon), [@carla](https://git.coopcloud.tech/carla)
* **Category**: Apps
* **Status**: 3, stable
* **Image**: [outlinewiki/outline](https://hub.docker.com/r/outlinewiki/outline), 4, upstream
@@ -19,15 +19,12 @@ Wiki and knowledge base for growing teams
1. Set up Docker Swarm and [`abra`]
2. Deploy [`coop-cloud/traefik`]
3. `abra app new ${REPO_NAME}`
- **WARNING**: Choose "n" when `abra` asks if you'd like to generate secrets
4. `abra app config YOURAPPNAME` - be sure to change `$DOMAIN` to something that resolves to
your Docker swarm box
5. Insert secrets:
- `abra app secret insert YOURAPPNAME secret_key v1 $(openssl rand -hex 32)` #12
3. `abra app new outline`
4. Insert secrets:
- `abra app secret insert YOURAPPNAME secret_key v1 $(openssl rand -hex 32)`
- `abra app secret generate -a YOURAPPNAME`
6. `abra app deploy YOURAPPNAME`
8. Open the configured domain in your browser to finish set-up
5. `abra app deploy YOURAPPNAME`
6. Open the configured domain in your browser to finish set-up
[`abra`]: https://git.coopcloud.tech/coop-cloud/abra
[`coop-cloud/traefik`]: https://git.coopcloud.tech/coop-cloud/traefik