fork for working with ci stuff (warn: force-pushing often in order to keep the logs clean)
Find a file
magmaus3 abd007c03a
Some checks failed
/ build (push) Has been cancelled
feat: add alpine ci
2025-05-31 18:49:27 +02:00
.cargo ignore humantime dep as tracing console-subscriber uses it (somewhere) 2025-03-11 21:15:11 -04:00
.forgejo feat: add alpine ci 2025-05-31 18:49:27 +02:00
.vscode chore: Add words to cspell dictionary 2025-04-15 22:35:39 +00:00
alpine feat: add alpine ci 2025-05-31 18:49:27 +02:00
arch chore: Add CONTINUWUITY_ environment variables 2025-05-10 12:54:33 +01:00
bin skip a few flakey complement tests 2025-03-15 19:14:45 -04:00
debian docs: Rename conduwuit to continuwuity in more places 2025-05-10 20:37:08 +01:00
docker build: Split docker target cache by target platform 2025-05-20 22:47:55 +01:00
docs docs: Security policy 2025-05-25 00:36:28 +01:00
nix/pkgs docs: Rename conduwuit to continuwuity in more places 2025-05-10 20:37:08 +01:00
src feat: For knock_restricted rooms, automatically join rooms we meet 2025-05-26 16:23:20 +00:00
tests update new complement flakes 2025-04-06 16:11:35 -04:00
theme chore: Fix typos across the codebase 2025-05-06 20:51:12 +01:00
.dockerignore chore: Docker ignore forgejo files 2025-05-20 21:31:41 +01:00
.editorconfig chore: Set editorconfig for workflows 2025-05-20 21:31:40 +01:00
.envrc load .env file before initializing flake to use DIRENV_DEVSHELL in .env 2024-06-03 00:10:28 -04:00
.git-blame-ignore-revs fix git blame ignore revs 2024-03-26 22:24:24 -04:00
.gitattributes Adds .gitattributes to the projects to prevent LN and CLRF conflicts. (#681) 2025-02-04 16:46:00 -05:00
.gitignore fix .gitignore to allow /target to be a symlink 2024-12-10 05:40:45 +00:00
.mailmap chore: Update Olivia Lee in mailmap 2025-04-15 21:58:39 +01:00
.markdownlintignore add markdownlint and run lychee in documentation CI workflow 2024-07-03 11:30:16 -04:00
.typos.toml docs: Rename conduwuit to continuwuity in more places 2025-05-10 20:37:08 +01:00
book.toml Update mdBook config for continuwuity 2025-04-16 15:49:46 +01:00
Cargo.lock chore: Upgrade deps 2025-05-21 15:28:46 +01:00
Cargo.toml chore: Allow raw string hashes for metadata crate 2025-05-20 21:36:00 +01:00
clippy.toml fix some nightly clippy lints 2025-03-13 08:37:34 -04:00
CODE_OF_CONDUCT.md Add maintainer emails 2025-04-27 18:36:57 +00:00
conduwuit-example.toml feat: Automatically set well-known support contacts 2025-05-21 20:32:53 +01:00
CONTRIBUTING.md docs: Rename conduwuit to continuwuity in more places 2025-05-10 20:37:08 +01:00
default.nix feat: support non-flake users 2024-02-11 21:56:55 -05:00
development.md docs: add some more conduwuit development info 2024-09-06 20:33:02 -04:00
engage.toml remove most of cargo test from engage as crane does that but with more caching 2025-03-11 21:09:24 -04:00
flake.lock bump ruwuma 2025-03-13 15:23:10 -04:00
flake.nix bump rust toolchain to 1.86.0 2025-04-05 18:37:13 -04:00
LICENSE remove nightly only feature, small housekeeping stuff 2023-11-29 21:59:18 -05:00
README.md docs: Badges for mirrors 2025-05-21 02:51:09 +01:00
renovate.json renovate: exclude rust deps we forked / cant easily bump or upgrade 2024-08-30 12:57:50 -04:00
rust-toolchain.toml bump rust toolchain to 1.86.0 2025-04-05 18:37:13 -04:00
rustfmt.toml bump nix lock, update to rust 2024 and 1.85.0 toolchain 2025-02-23 01:17:30 -05:00
SECURITY.md docs: Apply feedback on security policy 2025-05-26 15:01:58 +01:00

continuwuity

A community-driven Matrix homeserver in Rust

continuwuity is a Matrix homeserver written in Rust. It's a community continuation of the conduwuit homeserver.

forgejo.ellis.link

GitHub

Codeberg

Why does this exist?

The original conduwuit project has been archived and is no longer maintained. Rather than letting this Rust-based Matrix homeserver disappear, a group of community contributors have forked the project to continue its development, fix outstanding issues, and add new features.

We aim to provide a stable, well-maintained alternative for current conduwuit users and welcome newcomers seeking a lightweight, efficient Matrix homeserver.

Who are we?

We are a group of Matrix enthusiasts, developers and system administrators who have used conduwuit and believe in its potential. Our team includes both previous contributors to the original project and new developers who want to help maintain and improve this important piece of Matrix infrastructure.

We operate as an open community project, welcoming contributions from anyone interested in improving continuwuity.

What is Matrix?

Matrix is an open, federated, and extensible network for decentralized communication. Users from any Matrix homeserver can chat with users from all other homeservers over federation. Matrix is designed to be extensible and built on top of. You can even use bridges such as Matrix Appservices to communicate with users outside of Matrix, like a community on Discord.

What are the project's goals?

Continuwuity aims to:

  • Maintain a stable, reliable Matrix homeserver implementation in Rust
  • Improve compatibility and specification compliance with the Matrix protocol
  • Fix bugs and performance issues from the original conduwuit
  • Add missing features needed by homeserver administrators
  • Provide comprehensive documentation and easy deployment options
  • Create a sustainable development model for long-term maintenance
  • Keep a lightweight, efficient codebase that can run on modest hardware

Can I try it out?

Check out the documentation for installation instructions.

There are currently no open registration Continuwuity instances available.

What are we working on?

We're working our way through all of the issues in the Forgejo project.

Can I migrate my data from x?

  • Conduwuit: Yes
  • Conduit: No, database is now incompatible
  • Grapevine: No, database is now incompatible
  • Dendrite: No
  • Synapse: No

We haven't written up a guide on migrating from incompatible homeservers yet. Reach out to us if you need to do this!

Contribution

Development flow

  • Features / changes must developed in a separate branch
  • For each change, create a descriptive PR
  • Your code will be reviewed by one or more of the continuwuity developers
  • The branch will be deployed live on multiple tester's matrix servers to shake out bugs
  • Once all testers and reviewers have agreed, the PR will be merged to the main branch
  • The main branch will have nightly builds deployed to users on the cutting edge
  • Every week or two, a new release is cut.

The main branch is always green!

Policy on pulling from other forks

We welcome contributions from other forks of conduwuit, subject to our review process. When incorporating code from other forks:

  • All external contributions must go through our standard PR process
  • Code must meet our quality standards and pass tests
  • Code changes will require testing on multiple test servers before merging
  • Attribution will be given to original authors and forks
  • We prioritize stability and compatibility when evaluating external contributions
  • Features that align with our project goals will be given priority consideration

Contact

Join our Matrix room and space to chat with us about the project!