dolysis
/
conduwuit
mirror of https://github.com/girlbossceo/conduwuit.git
3
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
2,787 Commits 26 Branches 14 Tags 14 MiB
Rust 95.5%
Nix 1.8%
CSS 1.5%
Shell 0.6%
Python 0.6%
Go to file
strawberry ed5be58f9f ci: only run dockerhub steps if username and token are not empty 
Signed-off-by: strawberry <strawberry@puppygock.gay>
 		2024-04-02 00:32:41 -04:00
.gitea bit of repo cleanup 2024-01-31 21:12:09 -05:00
.github/workflows ci: only run dockerhub steps if username and token are not empty 2024-04-02 00:32:41 -04:00
.gitlab docs: build docs using mdBook, build in CI, deploy to gitlab pages 2024-03-19 00:17:41 -04:00
.vscode add EditorConfig vs code extension to recommendations 2024-03-26 22:24:24 -04:00
bin add back more verbose nix build logging (`-L`) 2024-03-08 12:51:21 -05:00
debian docs: build docs using mdBook, build in CI, deploy to gitlab pages 2024-03-19 00:17:41 -04:00
docker docs: build docs using mdBook, build in CI, deploy to gitlab pages 2024-03-19 00:17:41 -04:00
docs generalise and cleanup docs a bit 2024-03-30 22:06:18 -04:00
src fix: return error when trying to unregister unknown appservice id 2024-04-02 00:32:41 -04:00
tests move complement dir to tests dir 2024-04-02 00:32:41 -04:00
.dockerignore fix(ci): Only build in (remote host) docker and switch to glibc 2022-11-02 12:12:48 +01:00
.editorconfig chore: add EditorConfig 2024-03-16 00:09:48 -04:00
.envrc ci: cross compile static binaries for x86_64 and aarch64 2024-01-26 19:47:54 -05:00
.git-blame-ignore-revs fix git blame ignore revs 2024-03-26 22:24:24 -04:00
.gitignore add zed to .gitignore 2024-03-23 01:49:27 -04:00
.gitlab-ci.yml chore(deps): update docker docker tag to v26 2024-03-26 22:24:24 -04:00
CODE_OF_CONDUCT.md remove nightly only feature, small housekeeping stuff 2023-11-29 21:59:18 -05:00
Cargo.lock bump conduwuit version to 0.1.12 2024-04-02 00:32:41 -04:00
Cargo.toml bump conduwuit version to 0.1.12 2024-04-02 00:32:41 -04:00
LICENSE remove nightly only feature, small housekeeping stuff 2023-11-29 21:59:18 -05:00
README.md update differences.md 2024-03-30 22:06:18 -04:00
book.toml update book.toml for conduwuit 2024-03-23 01:49:27 -04:00
clippy.toml raise too-many-lines-threshold to 700 (for now?) 2024-03-26 22:24:24 -04:00
conduwuit-example.toml add lockdown_public_room_directory config option 2024-04-02 00:32:41 -04:00
default.nix feat: support non-flake users 2024-02-11 21:56:55 -05:00
engage.toml docs: build docs using mdBook, build in CI, deploy to gitlab pages 2024-03-19 00:17:41 -04:00
flake.lock bump rocksdb, switch to fork of rocksdb, bump flake 2024-03-30 22:06:18 -04:00
flake.nix bump rocksdb, switch to fork of rocksdb, bump flake 2024-03-30 22:06:18 -04:00
renovate.json ignore basically all the http dependencies we cant upgrade to 2024-02-14 09:51:11 -05:00
rust-toolchain.toml document github ci in rust-toolchain.toml 2024-03-10 13:03:28 -04:00
rustfmt.toml use chain_width 60 2024-03-26 22:24:24 -04:00

README.md

conduwuit

CI and Artifacts

a well maintained fork of Conduit

Visit the Conduwuit documentation for more information. Alternatively you can open docs/introduction.md in this repository.

What is Matrix?

Matrix is an open network for secure and decentralized communication. Users from every Matrix homeserver can chat with users from all other Matrix servers. You can even use bridges (also called Matrix Appservices) to communicate with users outside of Matrix, like a community on Discord.

What is the goal?

An efficient Matrix homeserver that's easy to set up and just works. You can install it on a mini-computer like the Raspberry Pi to host Matrix for your family, friends or company.

Can I try it out?

An official conduwuit server ran by me is available at transfem.dev (element.transfem.dev / cinny.transfem.dev)

What is the current status?

conduwuit is a fork of Conduit which is in beta, meaning you can join and participate in most Matrix rooms, but not all features are supported and you might run into bugs from time to time.

Why does this fork exist? Why don't you contribute back upstream?

I now intend on contributing back as time and mental energy sees fit, but my fork still exists as a way to:

  • avoid unnecessary Matrix and general developer politics
  • avoid bikeshedding unnecessary or irrelevant things in upstream MRs
  • Fast tracked bug fixes, performance improvements, security improvements, and new features
  • Have early access to MRs that may not be suitable/acceptable for Conduit (e.g. too niche, too advanced for general users, only being blocked due to pending on contributor actions that we can fix ourselves downstream, pending Matrix spec stuff, etc)
  • Support unspecced or WIP features
  • Have official support for other OS's like Windows, macOS, and BSD.
  • Have a stable testing ground for some MRs or new features and bug fixes

And various other reasons that may not be listed here.

How can I contribute?

  1. Look for an issue you would like to work on and make sure it's not assigned to other users
  2. Ask someone to assign the issue to you (comment on the issue or chat in #conduwuit:puppygock.gay)
  3. Fork the repo and work on the issue.
  4. Submit a PR (please keep contributions to the GitHub repo, main development is done here, not the GitLab repo which exists just as a mirror. If you are avoiding GitHub, feel free to join our Matrix chat to get your patch in.)

Contact

If you run into any question, feel free to

Donate

No official conduwuit logo exists. Repo and Matrix room picture is from bran (<3).

Is it conduwuit or Conduwuit?

Both.

Mirrors of conduwuit