DIMMiN Notes
My working notes related to the development of dimmin.com.
2026-06-20-Saturday
- Began rolling back some changes to the old trackerbot for the next update
- Decided to push to PostgreSQL in the next update to avoid the Database Migration issues that I was encountering before between SQLlite and Postgres
- Pivoted to updating the token rotation creds to using a Django Model instead of a rouge
tokens.dbSQLlite database to avoid.dockerignoreconflicts
2026-06-18-Thursday
- Used CNAME records instead of A Records to establish a connection between the Web Domain and the Virtual Machines on my Homelab, allowing remote access to a test Django server.
- Figured out how to add in the subdomains so I can access the site with
www. - Figured out how to establish redirect rules so that I could force redirects to
https://and use SSL Encryption - Learned about GitHub Actions which can be used to establish my CICD Pipeline
- Began creating SSH Deploy Keys for the test environment to start building out a CICD Pipeline
2026-06-16-Tuesday
- Started working on figuring out why I'm getting the 522 Response error when trying to establish a Cloudflare Tunnel between my Homelab and the internet.
2026-06-14-Sunday
- Created Proxmox Virtual Machines to attempt to self-host Catalixiahbot
- Installed Ubuntu server on these proxmox VMs
- Created a Cloudflare account to establish a Cloudflare Tunnel between my Virtual Machines and a new Web Domain
- Purchased a new Web Domain to try out my bot using
kidbottyy.xyz - Established a test server to associate with the new web domain
2026-06-13-Saturday
- Updated the
check_attendanceDjango Management Command to use the stored access token instead of needing to supply the access token as an arg - Began integrating listener data into the data pipeline for chat messages
2026-06-12-Friday
- Got Catalixiahbot up and running using twitchio v3.2.2
- Successfully handled OAuth flow and storage / rotation of tokens
- Managed to successfully record events that the previous version of twitchio was unable to capture (mainly capturing points redemptions now)
- Found that the connection remains stable and available for over 24 hours
2026-05-31-Sunday
- Double checked that the get chatters endpoint call with the
check_attendanceDjango Management Command worked as expected - Found that the latency was the primary issue when it came to slowing down the query (since the db is now a remote PostgreSQL connection)
2026-05-30-Saturday
- Created a Django Management Command that could call the
get_chattersREST API endpoint to manually check user attendance - Created the logic to save the response of this API call as an
Eventin the database - Built a signal to process this event to extract the attendances for each user based on whether they joined or left the chat