May: 13
Firecracker Endpoints
Section titled “Firecracker Endpoints”-
03:13PM
We will have two types of firecracker deployments, one that will be focused on one-shot runs, this can be useful for things like turning a transparent png into a webp. Or we could be converting an online video into a mp3, regardless this is mainly just to make easier to program and test around. Where this system will shine will be the ability to dynamically create endpoints for us to call! The pipeline will then become idea to python or node, once its a popular enough endpoint, we can expand it out into the rust code. Another area where this will be useful might be turning websites into markdown files for ai agents.
Axum KBVE Build Speeds
Section titled “Axum KBVE Build Speeds”-
06:51PM
A decent amount of the next updates are going towards trying to improve the astro and axum build for kbve.
Pool integration and optimization
Section titled “Pool integration and optimization”-
08:13PM
Before I go to grab some cofffe, I am going to focus on getting the replicas connected and utilized to avoid hitting our main database with older queries. We should maybe look at a valkey cache integration as well, but maybe the application itself could hold a cache, this would be an interesting way to handle it.
Bento Grid Astro
Section titled “Bento Grid Astro”-
01:05AM
Going to rebuild the bento grid for KBVE.com and try to use droid to offload the rendering and handling of the bento grid. I am thinking that we will have two grids, one that is managed by the off canvas and another that is handled by the main thread? Damn, actually I think it would make more sense to just focus on getting the grid out there and moving forward with the JSON.
Unity ECS
Section titled “Unity ECS”-
05:20PM
Migrating over from GameObjects to the ECS system. This might be a bit of a pain, but I am going to test case it before adding it into the RareIcon eco-system. That also means we would lose the Discord / web build, damn that will be a major blow to my original plans but hey it might be just worth it in the long term. Focusing on a Steam release should just be the goal, the rest can be for another day in the future.
Cypress
I am going to update the javascript notes with cypress documentation and information. We should also include a basic cheatsheet, that has the generic commands as a reference. Added a couple tables that outline the different cypress commands to run when building out the unit tests.
Next update to the Cypress will be adding the integration test for login! We will skip register because of the captcha.
Rome
Its a shame that rome is no longer an active tool, it would explain the errors that I was getting with it! So I updated the javascript document with a replacement tool, called Biome.js. While reading through the docs and setting up the extension, I saw an interesting github action called Review Dog, this was something that I was looking to build myself in the future. The review dog action basically helps streamline the automation of code review! 2024 is the year of automating some of the most boring aspects of development, unit testing and code reviews.
JukeBox
A couple future updates for the Jukebox? We should keep track of the songs that are being played, i.e a decently played id list, so that it does not play the same song again. This might be because the pool of songs is a bit too low, so the odds of a repeat are going to be higher! In addition to keeping track of the songs that have been played, I believe a skip option and maybe a ban/remove option? I will keep these ideas here for now, then whatever ones that need to be added, well I will first place them into the music mdx directly and then build them out within that week.
We could also make it so that the first video on pageload could be a default KBVE Jukebox video, that will be like 3 to 5 seconds long and it will act as a buffer, to prevent the first song to automatically get added.