Include .well-known in builds for Matrix federation #31
Labels
No Label
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No Milestone
No Assignees
2 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: autonomic-cooperative/autonomic.zone#31
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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?
I'm trying to enable federation for our new Matrix server but I need to include .well-known as described in this README.
So I got everything setup as described but I can't get it to show up. I even checked with this Matrix Federation test.
Maybe I am missing something. Any ideas?
I'm not super familar with Jekyll and it seems super hard to find anything Jekyll specific. I followed the tips in this article about including .well-know.
Include .well-known in buildsto Include .well-known in builds for Matrix federationI also found this monster Github thread.
I added a
.nojekyll
file in3ae5a6e803
No change though. Signing out for the night.
Tried
b3bed6d48e
, no luck ;)Maybe https://github.com/keybase/keybase-issues/issues/366#issuecomment-39044580?
My friend from fedi said: "Return the well-known straight from Nginx, so it is agnostic from the static site".
This sounds like a pretty excellent idea if we weren't using docker. Do you know a simple way of doing it?
Argh, what a pain. Yeah, I know how to do this now. We need to wire up an nginx container that tells traefik to match /.well-known/ on our main domain name. I'll get that out shortly.
Refs:
(PS. It'd be rad to be able to use nginx AND traefik because avoiding all these docker related hacks would be wonderful. But I can't see how that is possible without having to manage some weird configuration that we'll forget how it works really fast. Open to ideas though...)
We're ripping!
This is done done. Working.