conduit/complement
Charles Hall cf8f1f2546
make a bunch of changes so complement works again
Well, kinda. It crashed on me after 10 minutes because the tests timed
out like in <https://github.com/matrix-org/complement/issues/394>.
Sounds like this means it's a them problem though.

I want to use Nix to build this image instead in the future but this
will at least make it work for now and give me a reference for while I'm
porting it. I also want to make Conduit natively understand Complement's
requirements instead of `sed`ing a bunch of stuff and needing a reverse
proxy in the container. Should be more reliable that way.

I'm not making this run in CI until the above stuff is addressed and
until I can decide on a way to pin the revision of Complement being
tested against.
2024-01-27 18:09:43 -08:00
..
Dockerfile make a bunch of changes so complement works again 2024-01-27 18:09:43 -08:00
README.md make a bunch of changes so complement works again 2024-01-27 18:09:43 -08:00
caddy.json Complement improvements 2022-10-17 18:41:45 +02:00

README.md

Complement

What's that?

Have a look at its repository.

How do I use it with Conduit?

The script at ../bin/complement has automation for this. It takes a few command line arguments, you can read the script to find out what those are.