continuwuation/continuwuity

Fork 81

Update docs/configuration.mdx, Wrong ENVVARs #1412

Closed

lukasgen wants to merge 1 commit from lukasgen/continuwuity:lukasgen-documentation-patch-1 into main

lukasgen commented

2026-02-18 14:21:00 +00:00

First-time contributor

I tried 3 HOURS setting up the server, seemingly not my fault even
i am really frustrated with your documentation and have to admit that i didnt read anything to make this PR, but otherwise the docs keep getting neglected.
This software is very nice but the docs are disrespectful to it and slow down adoption...

... hope it helps out, sorry for being a jerk but ugh

I tried 3 HOURS setting up the server, seemingly not my fault even i am really frustrated with your documentation and have to admit that i didnt read anything to make this PR, but otherwise the docs keep getting neglected. This software is very nice but the docs are disrespectful to it and slow down adoption... ... hope it helps out, sorry for being a jerk but ugh

lukasgen added 1 commit

2026-02-18 14:21:00 +00:00

Update docs/configuration.mdx

Documentation / Build and Deploy Documentation (pull_request) Has been cancelled

Details

Checks / Prek / Pre-commit & Formatting (pull_request) Has been cancelled

Details

Checks / Prek / Clippy and Cargo Tests (pull_request) Has been cancelled

Details

4f5648d571

I tried 3 HOURS setting up the server, seemingly not my fault even

... hope it helps out... :/

ginger commented

2026-02-18 14:25:51 +00:00

Owner

Continuwuity accepts the legacy CONDUWUIT_ prefix for environment variables for backwards compatibility. Are you encountering issues using this prefix?

Continuwuity accepts the legacy `CONDUWUIT_` prefix for environment variables for backwards compatibility. Are you encountering issues using this prefix?

lukasgen commented

2026-02-18 14:41:32 +00:00

Author

First-time contributor

@ginger wrote in #1412 (comment):

Continuwuity accepts the legacy CONDUWUIT_ prefix for environment variables for backwards compatibility. Are you encountering issues using this prefix?

to be honest, i dont know...
i just want it to work on a basic docker compose.

TLDR:
Is there a working example of a compose.yml that just sets up all stuff instead of having to research this docs to a mindnumbing degree, just to give up and use XMPP? some .env files and this weird coturn conf?

ADHS fuled RANT:
i just want continuwuity with TURN and LiveKit via docker compose... i am honestly sick of trying to merge toml configuration of other documentation pages into the ENVVARS of the provided example, or porting the ENVARs to the config, squishing this TURNxLiveKit crap in 2,3,4 files and not getting it to run.
Please, i want to use this project, but its so frustrating to set it up. Just provide the admin some working compose.yml that i can just tell to set itself up? it would make others and my life easier...

i hate that its actually easier to use docker ansible matrix deploy or ESS and therefor be forced to use a bigger server.
meanwhile other admins that successfully programmed those files together telling me its "easy".
im tired...
... sorry for being a nuisance

@ginger wrote in https://forgejo.ellis.link/continuwuation/continuwuity/pulls/1412#issuecomment-24482: > Continuwuity accepts the legacy `CONDUWUIT_` prefix for environment variables for backwards compatibility. Are you encountering issues using this prefix? to be honest, i dont know... i just want it to work on a basic docker compose. TLDR: Is there a working example of a compose.yml that just sets up all stuff instead of having to research this docs to a mindnumbing degree, just to give up and use XMPP? some .env files and this weird coturn conf? ADHS fuled RANT: i just want continuwuity with TURN and LiveKit via docker compose... i am honestly sick of trying to merge toml configuration of other documentation pages into the ENVVARS of the provided example, or porting the ENVARs to the config, squishing this TURNxLiveKit crap in 2,3,4 files and not getting it to run. Please, i want to use this project, but its so frustrating to set it up. Just provide the admin some working compose.yml that i can just tell to set itself up? it would make others and my life easier... i hate that its actually easier to use docker ansible matrix deploy or ESS and therefor be forced to use a bigger server. meanwhile other admins that successfully programmed those files together telling me its "easy". im tired... ... sorry for being a nuisance

ginger commented

2026-02-18 14:42:47 +00:00

Owner

You should come join our chatroom using an account on another server -- we can help you more there. Closing this PR as it's not actually necessary.

You should come join [our chatroom](https://matrix.to/#/#continuwuity:continuwuity.org) using an account on another server -- we can help you more there. Closing this PR as it's not actually necessary.

ginger closed this pull request

2026-02-18 14:42:47 +00:00

Jade reviewed

2026-02-18 14:44:39 +00:00

Jade left a comment

Owner

The env variables are exactly equivalent, and we haven't seen any other issues with them.

Adding a note that conduwuit is supported along with conduit in the following paragraph would be good.

The env variables are [exactly equivalent](https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/src/core/config/mod.rs#L2372), and we haven't seen any other issues with them. Adding a note that conduwuit is supported along with conduit in the following paragraph would be good.

lukasgen commented

2026-02-18 14:45:54 +00:00

Author

First-time contributor

..sure, ill be there in a min