vault backup: 2026-05-01 11:54:44

01 Projects/video-accessibility-old/Video Accessibility Old.md

@@ -52,6 +52,9 @@ created: 2026-04-30
 ## Change Log
 | Date | Requested | Changed | Files |
 |------|-----------|---------|-------|
+| 2026-05-01 | Fix AD text sync, deploy to optical | Update text sync logic, redeploy container | transcription handler, docker config |
+| 2026-05-01 | Debug AD sync issue, deploy to optical | Fixed container image rebuild, added transcript logging, verified file sync | /opt/video-accessibility, container config |
+| 2026-05-01 | Docker image rebuild | Add volume mount for transcription file, rebuild image with updated code | Dockerfile, docker-compose.yml |
 | 2026-05-01 | AD text sync issue | Add file update logic on AD text change, set up server monitoring | transcription handler, optical server config |
 | 2026-05-01 | AD text sync issue, CC file upload test | File sync logic, logging, server deployment | video-accessibility codebase, transcription file, server logs |
 | 2026-05-01 | AD text sync issue | Added debug logging to transcript block, reviewed server logs | optical server /opt/video-accessibility, transcript handling code |

99 Daily/2026-05-01.md

@@ -98,3 +98,12 @@ tags: [daily]
 - 11:50 (<1min) | `video-accessibility-old`
   - **Asked:** Check why AD text updates aren't reflected in the transcription file and deploy changes to the optical server.
   - **Done:** Set up monitoring on the optical server and prepared to debug the CC file upload process via UI logs.
+- 11:53 | `video-accessibility-old`
+  - **Asked:** Fix AD text changes not reflecting in transcription file due to Docker image caching issue.
+  - **Done:** Identified root cause (code baked in Docker image without volume mount) and rebuilt the image to include file update logic.
+- 11:53 | `video-accessibility-old`
+  - **Asked:** Debug AD text update not reflecting in transcription file and deploy changes to optical server.
+  - **Done:** Identified image rebuild issue, deployed new container with updated code, and verified transcript logging functionality.
+- 11:53 | `video-accessibility-old`
+  - **Asked:** Fix AD text updates not reflecting in the transcription file and deploy changes to optical server.
+  - **Done:** Redeployed container with updated code on optical server and verified API startup; ready to test CC file upload.

wiki/tech-patterns/docker-volume-mounts-for-development-changes.md

@@ -0,0 +1,41 @@
+---
+tags: [tech-patterns, auto-generated]
+source: video-accessibility-old
+created: 2026-05-01
+---
+
+# Docker Volume Mounts for Development: Avoiding Baked Code Issues
+
+## When to use
+When deploying applications in Docker containers where code or configuration changes need to be reflected immediately without rebuilding the entire image. Prevents the common mistake of "baking in" code at build time and then wondering why file updates don't appear in the running container.
+
+## Prerequisites
+- Docker installed and running on the server
+- Application deployed in a Docker container
+- Need to iterate on code/configuration without full image rebuilds
+
+## Steps
+1. Identify files/directories that need live updates (e.g., transcription files, AD text configs)
+2. Instead of copying files into the image at build time, use Docker volume mounts in your docker-compose.yml or docker run command:
+   ```yaml
+   volumes:
+     - /opt/video-accessibility/data:/app/data
+     - /opt/video-accessibility/config:/app/config
+   ```
+3. For direct docker run: `docker run -v /opt/video-accessibility/data:/app/data ...`
+4. Update files on the host machine in the mounted directory
+5. Changes appear immediately in the running container without rebuilding the image
+
+## Key Configuration
+- **Dockerfile**: Remove `COPY` instructions for files that change frequently; use `VOLUME` declarations instead
+- **docker-compose.yml**: Add `volumes` section mapping host paths to container paths
+- **Permissions**: Ensure the container user has write permissions to mounted directories
+
+## Gotchas
+- Code baked into Docker images with `COPY` or `ADD` commands will not reflect host-side changes—the container uses the image snapshot
+- If changes don't appear, verify the volume mount path is correct and the container was restarted after mounting changes
+- File permissions between host and container can cause issues; use explicit user IDs if needed
+- Volume mounts only work for data/config; for code changes during development, either use volume mounts or implement a proper CI/CD pipeline for production
+
+## Source
+Project: video-accessibility-old