Test Article - Staging Deployment
VTVexa Team
December 3, 2025Test Article - Staging Deployment
This article is specifically for the staging environment to verify that:
- The webapp is fetching from the
dev/folder inblog_articlesrepo - GitHub API integration is working at runtime
- Blog content can be different between staging and production
How This Works
The staging deployment is configured with:
GITHUB_REPO_PATH=devThis tells the webapp to fetch blog posts from the dev/ folder instead of the root directory.
Benefits
- Separate Content: Test blog posts without affecting production
- Safe Testing: Preview content before publishing to main blog
- Environment Isolation: Staging and production have independent content
Deployment Verification
If you're reading this on the staging site, it means:
- Cloud Run deployment is working
- GitHub integration is configured correctly
- Blog fetching from
dev/folder successfully
Test Results
| Test Case | Status | Details |
|---|---|---|
| Cloud Run Deployment | Pass | Service deployed and accessible |
| GitHub API Integration | Pass | Successfully fetching from repository |
| Dev Folder Path | Pass | Reading from dev/ folder correctly |
| Markdown Rendering | Pass | Content displays properly |
| Environment Variables | Pass | GITHUB_REPO_PATH=dev configured |
| Blog List Loading | Pending | Verify all dev articles appear |
| Image Assets | Pending | Test image loading from dev folder |
| Navigation | Pending | Links between articles work |
| SEO Metadata | Pending | Verify frontmatter parsing |
| Performance | Pending | Check load times |
Next Steps
- Create more test articles in
dev/folder - When ready, move to root for production
- Set up GitHub webhook for auto-updates
Environment: Staging
Last Updated: December 3, 2025
Status: Test Article
Don't want to host it yourself?
Try Vexa Cloud for hassle-free meeting transcription with the same powerful API.