Learning Breakdown

[jm1021]

This issue is to start the learning process on understanding KASM.

1. Multi-Server
2. Workspace Creation
3. Database System

Documentation. https://nighthawkcoders.github.io/portfolio_2025/kasm/pages/intro

Participating in TLC sessions was a qualification for the Summer Internship!

1. It will not count toward intern hours, as it is not part of the funding request.
2. Going through TLC has helped you learn KASM usage which is a key skill before embarking on coding.
3. In the process of understanding, we should be aware hour count as we start updating documentation or performing system administration tasks to earn $$$'s.

Here are some key tasks. These will require documentation, coding, and administration.

1. Difficulty-Hard/Change-SmallRisk-/Low. The largest bug in the system is related to persistence. Reditt, Kasm Issues, S3, config error, or perhaps work on workspace: https://nighthawkcoders.github.io/portfolio_2025/kasm/multiserver/persistent
2. D-Medium,C-Large,R-High. To scale to a new High School, we need to consider adding a Teacher role/school, approval into KASM, and a High School assignment. Learning database migration and KASM APIs are a big part of this requirement. Possibly validate PUSD email. Log Poway, RB, MtC, DelNort, Westview. We could ask for the API from the district.
3. D-Medium, C-Small, R-High. We need to upgrade as soon as possible, prior to looking at persistence or database, this usually takes 1/2 hour. See if this eliminates the need for per-user licensing. https://kasmweb.com/docs/latest/upgrade/multi_server_upgrade.html#upgrade-script. Rachit (Driver, Navigator), The Plan needs to be exact. Rachit could be available if the student tried to contact. Test for more than 25 servers. Database backup.
4. D-Hardest, C-Large, R-Low. We need a refresh on Workspace. Part of the problem with KASM and S3 is the number of files the user creates. We need to move some of this activity to Workspace images. If it is bad, it is hard to debug because KASM gives little in diagnostics, due to its baby steps, but it takes time.
5. D-Medium, C-Medium, R-Medium. Rebranding everything from Nighthawk to Open Coding. DNS, Docker Hub, Registry Server, Workspace Name, ...
6. D-Easy, C-None, R-None. Getting active in Reddit and KASM support.
7. D-Hard, C-Big, R-None. Build up a full server set in California. Do it on 1.17 see if we can get it running. Leave 1.16 alone until it works. KASM documents for the whole thing, 1st hand.