<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/c84ef90ba1f040568418006e114c835b&quot; frameborder=&quot;0&quot; width=&quot;1280&quot; height=&quot;960&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>960</height><width>1280</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>960</thumbnail_height><thumbnail_width>1280</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/c84ef90ba1f040568418006e114c835b-ee7f08088478d662.gif</thumbnail_url><duration>491.271</duration><title>Database Backup and OpenID Implementation Overview</title><description>In today&apos;s video, I provided an overview of our progress on the project, highlighting that we completed user communication for our sign-up service and set up a PostgreSQL database for our matrix chat. I discussed the importance of database backups, specifically the implementation of point-in-time recovery (PITR) and a cron job for regular backups to GitHub. Tomorrow, we will be replacing the current Keycloak authentication system with OpenID, which requires careful planning and execution. I also outlined the tasks we&apos;ve accomplished so far, including Kubernetes setup and server configurations. Please ensure to review the cron job configurations and be prepared for the upcoming changes related to OpenID.</description></oembed>