Community maintained cdist types.
Go to file
evilham 87cc109bf1
[__jitsi_meet*] Make rooms on different domains not equivalent
This is a backwards-compatible change.

We switch the approach from "treat all domains as if they were the main domain"
to: "each domain has its own prosody settings".

This works perfectly fine, even with secured domains.

There is a caveat with secured domains, in that they use the main domain to log
in; this means that users are shared across all domains (as they were before
this commit).

This is due to jicofo refusing to start meetings from a domain that is not
configured, and it only accepting one domain.

Right now, this is acceptable, however we could want to authenticate against
e.g. different LDAP / IMAP servers in the future, so this would need addressing
at that stage.

Probably the best way to solve it is by patching jicofo, so it accepts starting
conferences from multiple domains and getting that patch upstream.

Sponsored by:   camilion.eu, eXO.cat
2022-04-21 13:20:30 +02:00
docs/src Generate documentation homepage from README 2021-01-11 11:34:54 +01:00
scripts Fix run-shellcheck.sh following 'conflict resolution' from gitlab web ui 2021-01-12 07:14:24 +01:00
type [__jitsi_meet*] Make rooms on different domains not equivalent 2022-04-21 13:20:30 +02:00
.gitignore Add basic CI configuration 2020-05-07 09:37:30 +02:00
.gitlab-ci.yml ci: do not run docs job in forks 2021-02-16 13:47:09 +01:00
LICENSE Initial project structure, README 2020-04-21 08:02:51 +02:00
Makefile Import html/man doc generation logic from upstream cdist 2021-01-04 11:08:55 +01:00
README.md Update cdist-recycledcloud URL in README 2021-02-16 13:36:29 +01:00

cdist-contrib

This project extends the cdist configuration management tool with community-maitained types which are either too specific to fit/be maintained in cdist itself or were not accepted in code cdist but could still be useful.

This project does not have releases and is continously updated: see git history for change log. You will find HTML documentation at contrib.cdi.st.

Using cdist-contrib

We would recommend that you clone this repository next to your regular cdist config directory, then setup conf_dir with relative paths in cdist configuration.

An example of this would be:

# contents of cdist.cfg next to cdist-contrib
[GLOBAL]
# Notice that types defined in last dir win and can override native types.
# Consider using a prefix for your own types to avoid collisions.
conf_dir = cdist-contrib:cdist-private

And you would run cdist from the same directory as follows:

cdist config -g cdist.cfg
# Or setup your CDIST_CONFIG_FILE environment variable and run as usual

Participating in the cdist community

Join us on #cdist:ungleich.ch on matrix!

Contributing

The preferred way to submit patches is by opening Merge Requests against the cdist-contrib project on code.ungleich.ch (you can make an account on account.ungleich.ch.

Every type in cdist-contrib must:

  • Have a man.rst documentation page.
  • Pass shellcheck without errors.

Other resources

Some people/organizations are known to keep some cdist types that might be of interest to others: