add dooris role for setup of dooris interaction on the node itself #129

Open
lilly wants to merge 2 commits from new-dooris-role into main
Owner
No description provided.
lilly self-assigned this 2026-07-19 17:01:35 +02:00
add dooris role for setup of dooris interaction on the node itself
Some checks failed
/ build (pull_request) Successful in 46s
/ Ansible Lint (push) Failing after 4m47s
/ Ansible Lint (pull_request) Failing after 4m58s
2abbb71788
You can view your changes at https://staging.infra-docs.hamburg.ccc.de/pr129/
lilly force-pushed new-dooris-role from 2abbb71788
Some checks failed
/ build (pull_request) Successful in 46s
/ Ansible Lint (push) Failing after 4m47s
/ Ansible Lint (pull_request) Failing after 4m58s
to 2be6c1e943
Some checks failed
/ build (pull_request) Successful in 28s
/ Ansible Lint (push) Failing after 2m47s
/ Ansible Lint (pull_request) Failing after 2m50s
2026-07-19 17:12:16 +02:00
Compare
lilly force-pushed new-dooris-role from 2be6c1e943
Some checks failed
/ build (pull_request) Successful in 28s
/ Ansible Lint (push) Failing after 2m47s
/ Ansible Lint (pull_request) Failing after 2m50s
to aec9ba7c12
All checks were successful
/ build (pull_request) Successful in 27s
/ Ansible Lint (pull_request) Successful in 2m33s
/ Ansible Lint (push) Successful in 2m35s
2026-07-19 17:32:33 +02:00
Compare
lilly changed title from WIP: add dooris role for setup of dooris interaction on the node itself to add dooris role for setup of dooris interaction on the node itself 2026-07-19 17:42:27 +02:00
lilly requested review from june 2026-07-19 17:42:32 +02:00
june left a comment

This looks good!
Just see the comments and two things:

  • Please add a README, see the forgejo_runner roles README as well as the certbot roles README for reference.
  • You pull in the docker_compose role as a dependency, which makes sense for having the directory be there of course. Thinking about this, we might want to pull in the entire docker config into the role (like we do for the Nextcloud role) or just add a comment to the README that the config must be provided externally. Think just clearing that up a bit like this avoids confusion in the future. In any case we can then also remove the host from the main docker compose group I suppose.
This looks good! Just see the comments and two things: - Please add a README, see the [`forgejo_runner` roles README](https://git.hamburg.ccc.de/CCCHH/ansible-infra/src/branch/main/roles/forgejo_runner/README.md) as well as the [`certbot` roles README](https://git.hamburg.ccc.de/CCCHH/ansible-infra/src/branch/main/roles/certbot/README.md) for reference. - You pull in the `docker_compose` role as a dependency, which makes sense for having the directory be there of course. Thinking about this, we might want to pull in the entire docker config into the role (like we do for the Nextcloud role) or just add a comment to the README that the config must be provided externally. Think just clearing that up a bit like this avoids confusion in the future. In any case we can then also remove the host from the main docker compose group I suppose.
@ -0,0 +2,4 @@
main:
options:
dooris_static_api_token:
Owner

Please add another underscore between role name and variable name to match the convention used in the other roles (so dooris__static_api_token).

Please add another underscore between role name and variable name to match the convention used in the other roles (so `dooris__static_api_token`).
lilly marked this conversation as resolved
@ -0,0 +7,4 @@
required: true
type: str
dooris_url:
Owner

Same here (so dooris__url).

Same here (so `dooris__url`).
lilly marked this conversation as resolved
lilly force-pushed new-dooris-role from aec9ba7c12
All checks were successful
/ build (pull_request) Successful in 27s
/ Ansible Lint (pull_request) Successful in 2m33s
/ Ansible Lint (push) Successful in 2m35s
to 5efa02c79d
Some checks failed
/ build (pull_request) Successful in 27s
/ Ansible Lint (push) Failing after 2m36s
/ Ansible Lint (pull_request) Failing after 2m40s
2026-07-23 18:58:05 +02:00
Compare
lilly force-pushed new-dooris-role from 5efa02c79d
Some checks failed
/ build (pull_request) Successful in 27s
/ Ansible Lint (push) Failing after 2m36s
/ Ansible Lint (pull_request) Failing after 2m40s
to af1b1906b1
Some checks failed
/ build (pull_request) Successful in 28s
/ Ansible Lint (push) Has been cancelled
/ Ansible Lint (pull_request) Has been cancelled
2026-07-23 19:03:28 +02:00
Compare
lilly force-pushed new-dooris-role from af1b1906b1
Some checks failed
/ build (pull_request) Successful in 28s
/ Ansible Lint (push) Has been cancelled
/ Ansible Lint (pull_request) Has been cancelled
to cf7b7ebbed
Some checks failed
/ build (pull_request) Successful in 29s
/ Ansible Lint (push) Failing after 3m15s
/ Ansible Lint (pull_request) Failing after 3m14s
2026-07-23 19:04:23 +02:00
Compare
Author
Owner

@june I have included the requested changes and inlined the dependency configuration into the new dooris role

@june I have included the requested changes and inlined the dependency configuration into the new `dooris` role
Some checks failed
/ build (pull_request) Successful in 29s
Required
Details
/ Ansible Lint (push) Failing after 3m15s
Required
Details
/ Ansible Lint (pull_request) Failing after 3m14s
Required
Details
This pull request doesn't have enough approvals yet. 0 of 1 approvals granted.
This branch is out-of-date with the base branch
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin new-dooris-role:new-dooris-role
git switch new-dooris-role
Sign in to join this conversation.
No description provided.