seth
/
jam-cloud
mirror of https://bitbucket.org/jamkazam/jam-cloud.git
1
0
Fork 0
Code Issues Actions Packages Projects Releases Wiki Activity

Update spec

This commit is contained in:
Seth Call 2026-03-01 16:23:18 -06:00
parent 7eba5fe10d
commit 281543d383
1 changed files with 2 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
web/ai/specs/infra-migration.md
View File

@ -59,7 +59,7 @@ The 1st development in this is going to skip CI/CD entirely, or to the greatest
We are going to focus on a local iteration driven flow that, say, I make a change locally in video/video-iac that's got k8s changes related to any of the above. I should always have a local terminal command I can run to sync that straight to the cluster, and have the change take effect immediately.
We want to codify all operations done from my machine with a `jkctl` master command. This command will have many useful subcommands, such as tailing logs or other operational helpers. But one such command would be `jkctl sync k8s`, which would sync the k8s configuration related to jam-cloud (but, for now, leaving alone the rest of the video/video-iac cluser ). `jkctl backup db` is another. So that's the actual 1st command we'd build.
We want to codify all operations done from my machine with a `jkctl` master command. This command will have many useful subcommands, such as tailing logs or other operational helpers. But one such command would be `jkctl k8s sync`, which would sync the k8s configuration related to jam-cloud (but, for now, leaving alone the rest of the video/video-iac cluser ). `jkctl db backup` is another. So that's the actual 1st command we'd build.
Let's make `jkctl` be ruby based for now. Given the order above.
@ -70,5 +70,4 @@ Other acceptable build technology will be dagger and gitea. We will retire use
When we are done, we'll need to do a similar cut-over for production. It won't be much different, and we can address a plan then, when we've gotten through this staging part successfully.
Suggestion: only have two k8s namespaces: jam-cloud-infra, and jam-cloud. jam-cloud-infra is for postgres, redis, rabbitmq, etc. jam-cloud will be for all the ruby-based apps and rapidly changing code, like `web`, `admin`, and `websocket-gateway`.