refactor: Rename all remaining conduwuit references to Continuwuity #2320

Open
Jade wants to merge 2 commits from jade/mass-rename into main
Owner

The big one...

Supersedes !1485 (adds an alias to the dockerfile, not planning on adding an entrypoint)
Closes #1536
Closes #2277 (Moves the alias to the correct location and adds some new aliases)

This pull request...

Pull request checklist:

  • This pull request targets the main branch, and the branch is named something other than
    main.
  • I have written an appropriate pull request title and my description is clear.
  • I understand I am responsible for the contents of this pull request.
  • I have followed the contributing guidelines:
The big one... Supersedes !1485 (adds an alias to the dockerfile, not planning on adding an entrypoint) Closes #1536 Closes #2277 (Moves the alias to the correct location and adds some new aliases) <!-- In order to help reviewers know what your pull request does at a glance, you should ensure that 1. Your PR title is a short, single sentence describing what you changed 2. You have described in more detail what you have changed, why you have changed it, what the intended effect is, and why you think this will be beneficial to the project. If you have made any potentially strange/questionable design choices, but didn't feel they'd benefit from code comments, please don't mention them here - after opening your pull request, go to "files changed", and click on the "+" symbol in the line number gutter, and attach comments to the lines that you think would benefit from some clarification. --> This pull request... <!-- Example: This pull request allows us to warp through time and space ten times faster than before by double-inverting the warp drive with hyperheated jump fluid, both making the drive faster and more efficient. This resolves the common issue where we have to wait more than 10 milliseconds to engage, use, and disengage the warp drive when travelling between galaxies. --> <!-- Closes: #... --> <!-- Fixes: #... --> <!-- Uncomment the above line(s) if your pull request fixes an issue or closes another pull request by superseding it. Replace `#...` with the issue/pr number, such as `#123`. --> **Pull request checklist:** <!-- You need to complete these before your PR can be considered. If you aren't sure about some, feel free to ask for clarification in #dev:continuwuity.org. --> - [x] This pull request targets the `main` branch, and the branch is named something other than `main`. - [x] I have written an appropriate pull request title and my description is clear. - [x] I understand I am responsible for the contents of this pull request. - I have followed the [contributing guidelines][c1]: - [x] My contribution follows the [code style][c2], if applicable. - [x] I ran [pre-commit checks][c1pc] before opening/drafting this pull request. - [x] I have [tested my contribution][c1t] (or proof-read it for documentation-only changes) myself, if applicable. This includes ensuring code compiles. - [x] My commit messages follow the [commit message format][c1cm] and are descriptive. <!-- Notes on these requirements: - While not required, we encourage you to sign your commits with GPG or SSH to attest the authenticity of your changes. - While we allow LLM-assisted contributions, we do not appreciate contributions that are low quality, which is typical of machine-generated contributions that have not had a lot of love and care from a human. Please do not open a PR if all you have done is asked ChatGPT to tidy up the codebase with a +-100,000 diff. - In the case of code style violations, reviewers may leave review comments/change requests indicating what the ideal change would look like. For example, a reviewer may suggest you lower a log level, or use `match` instead of `if/else` etc. - In the case of code style violations, pre-commit check failures, minor things like typos/spelling errors, and in some cases commit format violations, reviewers may modify your branch directly, typically by making changes and adding a commit. Particularly in the latter case, a reviewer may rebase your commits to squash "spammy" ones (like "fix", "fix", "actually fix"), and reword commit messages that don't satisfy the format. - Pull requests MUST pass the `Checks` CI workflows to be capable of being merged. This can only be bypassed in exceptional circumstances. If your CI flakes, let us know in matrix:r/dev:continuwuity.org. - Pull requests have to be based on the latest `main` commit before being merged. If the main branch changes while you're making your changes, you should make sure you rebase on main before opening a PR. Your branch will be rebased on main before it is merged if it has fallen behind. - We typically only do fast-forward merges, so your entire commit log will be included. Once in main, it's difficult to get out cleanly, so put on your best dress, smile for the cameras! --> [c1]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/CONTRIBUTING.md [c2]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/docs/development/code_style.mdx [c1pc]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/CONTRIBUTING.md#pre-commit-checks [c1t]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/CONTRIBUTING.md#running-tests-locally [c1cm]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/CONTRIBUTING.md#commit-messages
refactor: Rename all remaining conduwuit references to Continuwuity
Some checks failed
Checks / Changelog / Check changelog is added (pull_request_target) Has been cancelled
Documentation / Build and Deploy Documentation (pull_request) Has been cancelled
Checks / Prek / Pre-commit & Formatting (pull_request) Has been cancelled
Checks / Prek / Check changed files (pull_request) Has been cancelled
Checks / Prek / Clippy and Cargo Tests (pull_request) Has been cancelled
Update flake hashes / update-flake-hashes (pull_request) Has been cancelled
Auto Labeler / Apply labels based on changed files (pull_request_target) Successful in 7s
4386a50fa7
Also adds an alias for the old binary name to the dockerfile

Supersedes !1485
Closes #1536
Closes #2277
Jade force-pushed jade/mass-rename from 4386a50fa7
Some checks failed
Checks / Changelog / Check changelog is added (pull_request_target) Has been cancelled
Documentation / Build and Deploy Documentation (pull_request) Has been cancelled
Checks / Prek / Pre-commit & Formatting (pull_request) Has been cancelled
Checks / Prek / Check changed files (pull_request) Has been cancelled
Checks / Prek / Clippy and Cargo Tests (pull_request) Has been cancelled
Update flake hashes / update-flake-hashes (pull_request) Has been cancelled
Auto Labeler / Apply labels based on changed files (pull_request_target) Successful in 7s
to 67e5e11a97
Some checks failed
Documentation / Build and Deploy Documentation (pull_request) Successful in 1m24s
Checks / Prek / Check changed files (pull_request) Successful in 8s
Update flake hashes / update-flake-hashes (pull_request) Successful in 1m26s
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 1m53s
Checks / Changelog / Check changelog is added (pull_request_target) Failing after 16s
Checks / Prek / Clippy and Cargo Tests (pull_request) Successful in 8m43s
2026-10-04 23:59:33 +00:00
Compare
Owner

blocked: probably needs co-ordinating with package maintainers (ideally a due date)

blocked: probably needs co-ordinating with package maintainers (ideally a due date)
Author
Owner

Package maintainers seem to think it's OK

Package maintainers seem to think it's OK
docs: Chagelog
All checks were successful
Checks / Prek / Check changed files (pull_request) Successful in 11s
Documentation / Build and Deploy Documentation (pull_request) Successful in 1m9s
Update flake hashes / update-flake-hashes (pull_request) Successful in 1m22s
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 3m42s
Checks / Prek / Clippy and Cargo Tests (pull_request) Successful in 15m1s
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 11s
3cf7989abf
Jade 2026-10-06 20:10:34 +00:00
Henry-Hiles left a comment

Approved with my nix hat :3

Builds and runs with flake even beginning with an old database.

Approved with my nix hat :3 Builds and runs with flake even beginning with an old database.
nex approved these changes 2026-10-06 23:49:09 +00:00
@ -0,0 +16,4 @@
Environment="CONTINUWUITY_DATABASE_PATH=%S/continuwuity"
Environment="CONTINUWUITY_CONFIG_RELOAD_SIGNAL=true"
LoadCredential=continuwuity.toml:/etc/continuwuity/continuwuity.toml
Owner

not a systemd expert but these changes seem unsafe/very breaking. Will someone just updating passively from the debian repo encounter problems with this?

not a systemd expert but these changes seem unsafe/very breaking. Will someone just updating passively from the debian repo encounter problems with this?
Kimiblock left a comment

I'm still on vacation right now, so these are just preliminary findings.

I'm still on vacation right now, so these are just preliminary findings.
@ -0,0 +3,4 @@
Documentation=https://continuwuity.org/
Wants=network-online.target
After=network-online.target
Member

Not sure why we would remove this alias? Is Continuwuity no longer a drop-in replacement for conduwuit?

Not sure why we would remove this alias? Is Continuwuity no longer a drop-in replacement for conduwuit?
Author
Owner

It's in the wrong section of the file, check further down and #2277

It's in the wrong section of the file, check further down and #2277
@ -0,0 +13,4 @@
Environment="CONTINUWUITY_LOG_TO_JOURNALD=true"
Environment="CONTINUWUITY_JOURNALD_IDENTIFIER=%N"
Environment="CONTINUWUITY_DATABASE_PATH=%S/continuwuity"
Member

This would brick existing installations because the database path would not exist for State Directory/continuwuity. I would consider adding BindPaths=%S/conduwuit:%S/continuwuity (systemd.exec).

This would brick existing installations because the database path would not exist for State Directory/continuwuity. I would consider adding `BindPaths=%S/conduwuit:%S/continuwuity` ([systemd.exec](https://man.archlinux.org/man/systemd.exec.5.en#:~:text=BindPaths)).
@ -0,0 +55,4 @@
# ConfigurationDirectory isn't specified here because it's created by
# the distro's package manager.
StateDirectory=continuwuity
Member

Change of State Directory breaks existing database paths. Please work this around or announce this change.

Change of State Directory breaks existing database paths. Please work this around or announce this change.
@ -0,0 +56,4 @@
# ConfigurationDirectory isn't specified here because it's created by
# the distro's package manager.
StateDirectory=continuwuity
RuntimeDirectory=continuwuity
Member

Change of Runtime Directory breaks reverse proxy setups using UDS.

Change of Runtime Directory breaks reverse proxy setups using UDS.
Author
Owner

@Kimiblock Might it be worth keeping the old file (with the new binary location) and adding a new service with the new data/config locations, allowing people to manually move stuff and then switch over? I don't really know systemd services for host binaries that well

@Kimiblock Might it be worth keeping the old file (with the new binary location) and adding a new service with the new data/config locations, allowing people to manually move stuff and then switch over? I don't really know systemd services for host binaries that well
Member

Yeah, I think adding a new service and keeping the old one untouched is the proper approach.

We could also add a reminder to migrate in Continuwuity itself. Specifically, the old continuwuity.service can add special environment variables and Continuwuity would detect this and send a migration reminder notification via the admin account.

Yeah, I think adding a new service and keeping the old one untouched is the proper approach. We could also add a reminder to migrate in Continuwuity itself. Specifically, the old continuwuity.service can add special environment variables and Continuwuity would detect this and send a migration reminder notification via the admin account.
@ -87,0 +83,4 @@
# Equivalent to `!admin users create_user jade`
./continuwuity --execute "users create_user jade"
INFO continuwuity_service::admin::startup: Startup command #0 completed:
Created user with user_id: @jade:continuwuity.org and password: `<redacted>`
Member

Can this be example.com to match with rest of docs? Just a nit, keeping is fine

Can this be `example.com` to match with rest of docs? Just a nit, keeping is fine
Member

Kindly remove the info block on docs/deploying.mdx as well (here)

Kindly remove the info block on `docs/deploying.mdx` as well ([here](https://forgejo.ellis.link/continuwuation/continuwuity/src/commit/2fad908f278416c14c60221097d405de871505d9/docs/deploying.mdx))
All checks were successful
Checks / Prek / Check changed files (pull_request) Successful in 11s
Required
Details
Documentation / Build and Deploy Documentation (pull_request) Successful in 1m9s
Update flake hashes / update-flake-hashes (pull_request) Successful in 1m22s
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 3m42s
Required
Details
Checks / Prek / Clippy and Cargo Tests (pull_request) Successful in 15m1s
Required
Details
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 11s
Required
Details
This pull request has changes conflicting with the target branch.
  • Cargo.lock
  • src/api/client/unversioned.rs
  • src/api/server/event_auth.rs
  • src/api/server/get_missing_events.rs
  • src/api/server/make_join.rs
  • src/main/runtime.rs
  • src/main/server.rs
  • src/service/antispam/mod.rs
  • src/service/federation/execute.rs
  • src/service/federation/mod.rs
  • src/service/media/mod.rs
  • src/service/pusher/webpush/mod.rs
  • src/service/rooms/event_handler/mod.rs
  • src/service/rooms/event_handler/policy_server.rs
  • src/web/pages/components/mod.rs
  • src/web/pages/oauth/grant.rs
View command line instructions

Manual merge helper

Use this merge commit message when completing the merge manually.

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin jade/mass-rename:jade/mass-rename
git switch jade/mass-rename
Sign in to join this conversation.
No reviewers
nex
continuwuation/Package-Maintainers
No milestone
No assignees
5 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
continuwuation/continuwuity!2320
No description provided.