Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
M
matrix-media-repo
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Package Registry
Container Registry
Model registry
Operate
Terraform modules
Monitor
Service Desk
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
TeDomum
matrix-media-repo
Commits
a3a7ac5b
Commit
a3a7ac5b
authored
5 years ago
by
Travis Ralston
Browse files
Options
Downloads
Patches
Plain Diff
Per-domain configs are now a thing
parent
c8d3f5a4
Loading
Loading
Loading
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
docs/config.md
+1
-1
1 addition, 1 deletion
docs/config.md
with
1 addition
and
1 deletion
docs/config.md
+
1
−
1
View file @
a3a7ac5b
...
...
@@ -21,7 +21,7 @@ As it loads each file, it overrides whatever the file has defined.
Simply put, given
`00-main.yaml`
,
`01-bind.yaml`
, and
`02-datastores.yaml`
the media repo will read the defaults, then
apply 00, then 01, then 02. The file names do not matter aside from application order.
## Per-domain configs
(not yet implemented)
## Per-domain configs
When using per-domain configs the
`homeservers`
field of the main config can be ignored. The
`homeservers`
option
is still respected for simple configuration of domains, though it is recommended to use per-domain configs if you're
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment