docs(docker): Big refactor with better structuring, simplified examples, and other improvements #1594
No reviewers
Labels
No labels
Blocked
Bug
Changelog
Added
Changelog
Missing
Changelog
None
Cherry-picking
Database
Dependencies
Dependencies/Renovate
Difficulty
Easy
Difficulty
Hard
Difficulty
Medium
Documentation
Enhancement
Good first issue
Help wanted
Inherited
Matrix/Administration
Matrix/Appservices
Matrix/Auth
Matrix/Client
Matrix/Core
Matrix/E2EE
Matrix/Federation
Matrix/Hydra
Matrix/MSC
Matrix/Media
Matrix/T&S
Merge
Merge/Manual
Merge/Squash
Meta
Meta/CI
Meta/Packaging
Priority
Blocking
Priority
High
Priority
Low
Security
Status
Confirmed
Status
Duplicate
Status
Invalid
Status
Needs Investigation
Support
Wont fix
old/ci/cd
old/rust
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
continuwuation/continuwuity!1594
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "stratself/continuwuity:stratself/docs-docker-improvements"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This pull request essentially refactor the Docker deploying docs and include many new changes. Since this has many huge changes, I believe submitting it early as WIP would help with extensive reviews.
As mentioned in #1508, essentially complete these items:
and genericinstructions to match the new registration flow from #1367docker-compose.with-caddy.ymlconfigs:file for the/etc/resolv.confmount, withnameserver 1.1.1.1as content. This would stop people from footgunning themselves with localhost nameserversIt also adds the following niceties:
docs/public/deployingto allow them to be viewable as raw files on the website.Todos
Some more changes for coherency will be needed.
This would conflict with @ky-bean's #1553. LIkely, I would copy-and-paste their docs into mine, and mark them as Co-Contributor.
Questions
The big question right now: Should I include
.well-knowndelegation on:443in the examples, or not? For Caddy it should be simple enough not to do that. But for Traefik (especially when integrating with existing Traefik), it'd simplify the number of ports opened.Pull request checklist:
mainbranch, and the branch is named something other thanmain.myself, if applicable. This includes ensuring code compiles.
Here's a preview
I had to disable dead link checking to get the yaml URLs to build. It could be nice if this can be toggled only for this page
b9ff72e82589e87626cc8661fefb08c4a409e3b8WIP: docs(docker): Big refactor with better structuring, simplified examples, and other improvementsto docs(docker): Big refactor with better structuring, simplified examples, and other improvementsdocs(docker): Big refactor with better structuring, simplified examples, and other improvementsto WIP: docs(docker): Big refactor with better structuring, simplified examples, and other improvementsd61ed33f54b11e2670940ee3675b9c042b4c5d21WIP: docs(docker): Big refactor with better structuring, simplified examples, and other improvementsto docs(docker): Big refactor with better structuring, simplified examples, and other improvementsRemoving WIP status, as it should be reviewable now. Apologies for the large diffs.
@ -170,2 +46,3 @@for more details and alternative solutions.:::tip Split-domain setupsFor more setups with `.well-known` delegation and split-domain deployments, consult the [Delegation/Split-domain](../advanced/delegation) page.:::Might want an additional warning that the server_name cannot be changed
@ -174,0 +103,4 @@- `CONTINUWUITY_SERVER_NAME` - Your Matrix server's domain name.- `CONTINUWUITY_DATABASE_PATH` - Where to store your database. This must match the docker volume mount.- `CONTINUWUITY_ADDRESS` - Bind address (use `0.0.0.0` to listen on all interfaces).In docker,
CONTINUWUITY_ADDRESSrefers to the address bound inside the container. Unlike on a host deployment, you typically want to bind to all interfaces, because requests from other containers (and the host) don't come from localhost, but come from internal IPs. When using docker's port forwarding, docker controls what interfaces are forwarded to the container.that is to say, this option won't do what non-docker people expect.
Added pendantic note "(for docker, use
0.0.0.0)"bf01ad01bf807e7d4665Moved "Docker (Quick Test)" and build instructions to an umbrella section called "Other Deployment Options". I think it is better suited there as docker cli alone was never meant for serious prod. Webpage also updated
matrix.subdomains in composes #1660