Fachschaft/nixConfig
6
2
Fork 2
Code Issues 10 Pull requests 1 Projects Wiki Activity

Centralized Postgres / Database for Stalwart #50

New issue
Open
opened 2025-02-26 15:16:43 +00:00 by nerf · 0 comments
nerf commented 2025-02-26 15:16:43 +00:00
Owner
Copy link

Right now the database for stallwart is sqlite on nyarlathotep.
When we start handing out mailboxes these will live in this database (at least for a big part).
Beforehand it will only contain some config and things like DKIM parameters.

We might want to get this in a more mature database solution, and if we do this we might want to think about rolling a centralized
database store where all machines can connect to. This has benefits for making backups and redeployments easier.

Originally posted by @nerf in #47/files (comment)

Right now the database for stallwart is sqlite on nyarlathotep. When we start handing out mailboxes these will live in this database (at least for a big part). Beforehand it will only contain some config and things like DKIM parameters. We might want to get this in a more mature database solution, and if we do this we might want to think about rolling a centralized database store where all machines can connect to. This has benefits for making backups and redeployments easier. _Originally posted by @nerf in https://gitea.mathebau.de/Fachschaft/nixConfig/pulls/47/files#issuecomment-1102_
nerf changed title from Centralized Postgres to Centralized Postgres / Database for Stalwart 2025-02-26 15:19:24 +00:00
nerf added this to the Mail is just working milestone 2025-03-27 10:09:00 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
No results found.
Labels
Clear labels   
Kind/Breaking

Breaking change that won't be backward compatible

  
Kind/Bug

Something is not working

  
Kind/Documentation

Documentation changes

  
Kind/Enhancement

Improve existing functionality

  
Kind/Feature

New functionality

  
Kind/Security

This is security issue

  
Kind/Testing

Issue or pull request related to testing

  
Priority
Critical
The priority is critical

  
Priority
High
The priority is high

  
Priority
Low
The priority is low

  
Priority
Medium
The priority is medium

  
Reviewed
Confirmed
Issue has been confirmed

  
Reviewed
Duplicate
This issue or pull request already exists

  
Reviewed
Invalid
Invalid issue

  
Reviewed
Won't Fix
This issue won't be fixed

  
Status
Abandoned
Somebody has started to work on this but abandoned work

  
Status
Blocked
Something is blocking this issue or pull request

  
Status
Need More Info
Feedback is required to reproduce issue or to continue work

No labels
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
Milestone
Clear milestone
No items
No milestone
Mail is just working
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
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: Fachschaft/nixConfig#50
No description provided.
Delete branch "%!s()"

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?