bytelyst/learning_ai_common_plat
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(devops): refresh Track A handoff status

Browse Source
This commit is contained in:
root 2026-03-30 00:11:45 +00:00
parent 5cff282961
commit bb85bf6176
1 changed files with 23 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

32
docs/devops/vercel/TRACK_A_HANDOFF_2026-03-29.md
View File

@ -30,24 +30,31 @@ Architecture decision after this handoff:
### 1. DNS is not ready
From the VM, these records did not resolve at the time of the original session:
At the time of the original session, these records did not resolve from the VM:
- `api.bytelyst.com`
- `gitea.bytelyst.com`
- `admin.bytelyst.com`
- `tracker.bytelyst.com`
For the revised architecture, only `api.bytelyst.com` and `gitea.bytelyst.com` must resolve to the VM for Track A. `admin.bytelyst.com` and `tracker.bytelyst.com` should resolve to Vercel instead.
For the revised architecture:
### 2. Azure CLI is missing
- `api.bytelyst.com` and `gitea.bytelyst.com` must resolve to the VM
- `admin.bytelyst.com` and `tracker.bytelyst.com` should resolve to Vercel, not the VM
`az account show` failed with:
Only the VM-hosted records are prerequisites for A1/A2/A4.
```text
az: command not found
```
### 2. Azure CLI is installed, but the active subscription context still needs validation
That blocks A4 because the NSG cannot be snapshotted or edited from this VM.
Azure CLI is now installed and `az account show` succeeds.
Current observed context:
- subscription: `Azure subscription 1`
- tenant: `eScube`
- state: `Disabled`
This means A4 is no longer blocked by a missing CLI, but it may still be blocked until the correct active subscription is selected and has permission to manage the VM NSG.
### 3. Linux build host is still using the wrong Gitea registry hostname
@ -75,7 +82,14 @@ curl -sf https://api.ipify.org && echo
```
3. Point `admin.bytelyst.com` and `tracker.bytelyst.com` at Vercel, not the VM.
4. Install Azure CLI and log in with permissions to manage the VM NSG.
4. Verify Azure account context and switch to the correct active subscription if needed:
```bash
az account show -o table
az account list -o table
az account set --subscription "<active-subscription-name-or-id>"
```
5. Export a Linux-safe Gitea host before rebuilds, for example:
```bash