video-query/frontend
2025-11-06 18:06:43 +05:30
..
public new features with video job cycles and video lenght changes 2025-10-22 14:24:13 +05:30
src Video-Batch and Long Video Working 2025-11-06 18:06:43 +05:30
.env new features with video job cycles and video lenght changes 2025-10-22 14:24:13 +05:30
build.sh significant code changes and new config file to accommodate deploying to different server with different paths and URLs 2025-09-18 17:55:30 -05:00
CONFIG_README.md new features with video job cycles and video lenght changes 2025-10-22 14:24:13 +05:30
package-lock.json new features with video job cycles and video lenght changes 2025-10-22 14:24:13 +05:30
package.json significant code changes and new config file to accommodate deploying to different server with different paths and URLs 2025-09-18 17:55:30 -05:00
README.md initial commit 2025-09-18 14:25:24 -05:00
requirements.txt initial commit 2025-09-18 14:25:24 -05:00

Video Query Frontend

This is the frontend for the Video Query application.

Development

npm install
npm start

Building for Production

To build the application for deployment at the /video_query path:

# Option 1: Use the build script (recommended)
./build.sh

# Option 2: Manual build with correct PUBLIC_URL
PUBLIC_URL=/video_query npm run build

Deployment

After building, deploy the contents of the build directory to your web server:

# Example deployment command
scp -r build/* user@server:/var/www/html/video_query/

Troubleshooting

Static Assets Not Loading

If you see errors like:

Loading failed for the <script> with source "https://ai-sandbox.oliver.solutions/static/js/main.xxx.js"

This means the application is looking for static assets at the wrong path. Make sure:

  1. You built the application with PUBLIC_URL=/video_query
  2. The .env file contains PUBLIC_URL=/video_query
  3. The files are deployed to the correct directory on the server

Authentication Issues

If you encounter authentication issues:

  1. Verify the redirect URI in src/auth/authConfig.js matches your deployment URL
  2. Ensure the application is registered correctly in Azure AD
  3. Check browser console for specific authentication errors