| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
Full reasoning under "Decisions" section inside TODOs.org.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I was able to make matterbridge work, but only to realize that it doesn't
support private groups on most services. So I can't use this as a replacement
for other chat systems as I desired.
I ended up using my conversations.im account due to the lack of MUC support in
my current server.
I was also able to setup the Converse client, but my Prosody server also doesn't
have HTTP (or WebSockets, I don't remember) yet, so it didn't work for my
server.
So this may serve as a useful future reference, but I pan to turn off the
matterbridge server itself.
|
| |
|
|
| |
Use NGINX to create TLS certificate and then share it with prosody.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
After a terraform state rm '...' of the server and domain configuration, and
recreating the instance again while leaving the dettached one running.
I had to do this because I was experimenting too much with the domain and I hit
the Let's Encrypt rate limit[0].
Because of that I'll recreate certificates less often so that doesn't happen in
the new domain during development of the VPS.
I'm not shure if this solution works, but I'll commit just as a checkpoint. I
had to change the custom DNS nameservers from Digital Ocean to Vultr and that
may take a while, so it's worth having this as a checkpoint in time while I'm
off to other things.
[0]: https://letsencrypt.org/docs/rate-limits/
|
| | |
|
| |
|
|
|
| |
This option is to override the global one. Since they are the same, it has no
effect.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
The TLS setup for Prosody is broken, though.
|
| | |
|
| | |
|
| | |
|
| |
|
