MEDLab/Handbook
5
0
Fork 1
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Added more context on various tools

Browse Source
This commit is contained in:
ntnsndr
2026-08-24 19:37:43 +00:00
parent 8caca4f794
commit 8f0120b726
1 changed files with 8 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/technology.md
+8 -8
View File
@@ -20,19 +20,19 @@ For more context on our approach, see James Brennan and Nathan Schneider, “[La
**How it works**: MEDLab users can log into the Gitea system with their MEDLab credentials using the “Sign in with Cloudron” log-in. You may need to manually add a password to your account to push via HTTPS. **How it works**: MEDLab users can log into the Gitea system with their MEDLab credentials using the “Sign in with Cloudron” log-in. You may need to manually add a password to your account to push via HTTPS.
CI processes are possible through the runner located at the MEDLab [GitLab account](https://gitlab.com/medlabboulder). External users can create accounts on our Gitea server, but they must be manually approved.
CI processes are possible through the runner located at the MEDLab [GitLab account](https://gitlab.com/medlabboulder). It is not recommended to run runners on the same server as Gitea.
## Newsletter ## Newsletter
`newsletter.medlab.host` `newsletter.medlab.host`
**What it is**: We send an occasional newsletter through a self-hosted platform called Listmonk, combined with the campus Google Groups system. **What it is**: We send an occasional newsletter through a self-hosted platform called Listmonk, which sends email through our campus AWS system.
**How to use it**: In Listmonk, create a newsletter using the Google Groups template, targeted at the Google Groups list. Be sure to send a test message to \`medlab@colorado.edu\` before sending. Upon sending, the email will go to both that address and the Google Groups list, where it will be held for moderation. Nathan is the admin and all posts must be manually approved. **How to use it**: In Listmonk, copy a previous campaign using the MEDLab Newsletter list. Be sure to send a test message before sending.
Lately, this method has not been working, because the Google Group has been blocking the newsletter.app@medlab.host address. Try this: just send yourself a draft and resend that to the list. The reason we use AWS is that sending email in bulk can be complex from the perspective of server resources, and emails from weird servers like \`medlab.host\` are likely to be flagged as spam.
The reason we use Google Groups is that sending email in bulk can be complex from the perspective of server resources, and emails from weird servers like \`medlab.host\` are likely to be flagged as spam.
## Nextcloud ## Nextcloud
@@ -63,9 +63,9 @@ When logging in, log in with Cloudron rather than the app's native login fields.
`cloud.medlab.host/apps/riotchat` `cloud.medlab.host/apps/riotchat`
**What it is**: [Matrix](https://matrix.org "https://matrix.org") is a FLOSS communications protocol intended to be a highly secure backend for chat, email, social media, and other applications. It is still early-stage, but it a very promising project, and it has already been adopted by several European governments seeking to reduce their dependence on US-based software companies. Rather than relying on centralized companies, it enables both federated and peer-to-peer connections. Our own instance is currently not federated with the wider Matrix network, as we only use it internally, but we could add this functionality if we see fit. We use Element, which is the flagship Matrix client; Element used to be called “Riot,” which is why that's in the URL on NextCloud. **What it is**: [Matrix](https://matrix.org "https://matrix.org") is a FLOSS communications protocol intended to be a highly secure backend for chat, email, social media, and other applications. It is still early-stage, but it a very promising project, and it has already been adopted by several European governments seeking to reduce their dependence on US-based software companies. Rather than relying on centralized companies, it enables both federated and peer-to-peer connections. Our own instance is currently not federated with the wider Matrix network, as we only use it internally, but we could add this functionality if we see fit. We use Element, which is the flagship Matrix client; Element used to be called “Riot,” which is why that's in the URL on Nextcloud.
**How it works**: Access it through the Element client from within NextCloud, or using a Matrix-compatible mobile app (such as the one also called Element). The server is hosted on Cloudron at `matrix.medlab.host` (which you only need to know if you're logging in through a mobile client; the Web client already knows this). When first logging in, it will ask you to create a security key, which is a long series of characters. Keep that someplace safe. Hopefully you won't need to use it very often. Log in with the same credentials you use for Nextcloud. Be sure to join the MEDLab Space to access all our rooms. **How it works**: Access it through the Element client from within Nextcloud, or using a Matrix-compatible mobile app (such as the one also called Element). The server is hosted on Cloudron at `matrix.medlab.host` (which you only need to know if you're logging in through a mobile client; the Web client already knows this). When first logging in, it will ask you to create a security key, which is a long series of characters. Keep that someplace safe. Hopefully you won't need to use it very often. Log in with the same credentials you use for Nextcloud. Be sure to join the MEDLab Space to access all our rooms.
You can use any of the many [Matrix clients](https://matrix.org/ecosystem/clients/ "https://matrix.org/ecosystem/clients/") with our chat system, including mobile apps. You can use any of the many [Matrix clients](https://matrix.org/ecosystem/clients/ "https://matrix.org/ecosystem/clients/") with our chat system, including mobile apps.