matrix-org / matrix-org/mjolnir
Postgres backend schema management in the appservice
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 445
- Forks
- 75
- Avg merge
- 2d 44m
- Merged PRs (30d)
- 3
Description
Currently we create tables adhoc https://github.com/matrix-org/mjolnir/blob/ec4cb2e93c02799b86f0f577a0adbacd9cbacab4/mx-tester.yml#L9
We could potentially rely on https://github.com/matrix-org/matrix-appservice-bridge/pull/442 for this, but we could handle it ourselves if review is taking too long. This is the same pattern used by the other bridges and can be copied pretty closely.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the table-creation setup referenced at mx-tester.yml line 9, then compare the schema-management pattern used by the other bridges. Done means the appservice manages its Postgres schema instead of creating tables ad hoc, with the chosen approach consistent with the linked matrix-appservice-bridge work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql, typescript
- Domain
- backend, database
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100