SipsOfCode/infrastructure
2
2
Fork 0
Code Issues 5 Pull requests 4 Releases Activity

feat(hedgedoc): add quadlet-managed hedgedoc role #97

Merged
saibotk merged 1 commit from add-hedgedoc into main 2025-03-23 22:30:20 +01:00
Conversation 1 Commits 1 Files changed 10 +355
saibotk commented 2025-03-17 00:37:01 +01:00
Owner
Copy link

This adds a hedgedoc installation role for running hedgedoc with postgres and local file uploads.

It can be configured entirely via ENV vars to do anything though.

This adds a hedgedoc installation role for running hedgedoc with postgres and local file uploads. It can be configured entirely via ENV vars to do anything though.
saibotk self-assigned this 2025-03-17 00:37:01 +01:00
feat(hedgedoc): add quadlet-managed hedgedoc role
All checks were successful
ci/woodpecker/pr/ansible-lint Pipeline was successful
Details
0ac960b786
 
This adds a hedgedoc installation role for running hedgedoc with postgres and local file uploads.

It can be configured entirely via ENV vars to do anything though.
requested review from histalek 2025-03-17 00:37:06 +01:00
saibotk force-pushed add-hedgedoc from 0ac960b786 to 279bc41586 2025-03-17 00:40:33 +01:00 Compare
histalek approved these changes 2025-03-18 20:35:56 +01:00
roles/hedgedoc/defaults/main.yml Outdated
@ -0,0 +38,4 @@
DB_USERNAME: hedgedoc
DB_PASSWORD: "{{ hedgedoc_postgres_database_password }}"
DB_DATABASE: hedgedoc
DB_HOST: /var/run/postgresql
histalek commented 2025-03-18 20:31:40 +01:00
Owner
Copy link

This is the only supported value, right? shouldn't we hardcode this then?

This is the only supported value, right? shouldn't we hardcode this then?
saibotk commented 2025-03-18 20:54:34 +01:00
Author
Owner
Copy link

jeah, i will do that.

I thought about it and did so for mastodon i think, but this was not done in some other roles, so i also did not directly implement this here.

Going forward i'd like to keep some document in here with some design decisions, where we can document stuff like this and just agree that such values should not be easily overrideable by a user.

jeah, i will do that. I thought about it and did so for mastodon i think, but this was not done in some other roles, so i also did not directly implement this here. Going forward i'd like to keep some document in here with some design decisions, where we can document stuff like this and just agree that such values should not be easily overrideable by a user.
👍 1
histalek marked this conversation as resolved
saibotk force-pushed add-hedgedoc from 279bc41586 to 451d2539b0 2025-03-23 22:28:33 +01:00 Compare
saibotk deleted branch add-hedgedoc 2025-03-23 22:30:21 +01:00
Sign in to join this conversation.
Reviewers
No reviewers
histalek
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
saibotk
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: SipsOfCode/infrastructure#97
No description provided.
Delete branch "add-hedgedoc"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?