Fix jwt-token

client/.env.development

@@ -0,0 +1,2 @@
+# Development environment - runs on root path
+VITE_BASE_PATH=

client/.env.example

@@ -1,9 +1,11 @@
 # Client Environment Configuration
 
 # Base path for the application (used for deployment in subdirectories)
-# Default: '/drones' in production, '' in development
+# Examples:
-# Example: VITE_BASE_PATH=/my-custom-path
+#   For root deployment: VITE_BASE_PATH=/
-# VITE_BASE_PATH=
+#   For subdirectory deployment: VITE_BASE_PATH=/uggla/
+#   Leave empty for default (root): VITE_BASE_PATH=
+VITE_BASE_PATH=/uggla/
 
 # API URL override (if API is hosted on different domain/port)
 # Default: auto-detected based on environment

client/.env.production

@@ -0,0 +1,2 @@
+# Production environment - deployed under /uggla/ path
+VITE_BASE_PATH=/uggla/

client/src/config/app.js

@@ -1,8 +1,7 @@
-// Application configuration
+// Application configuration from environment variables
 export const APP_CONFIG = {
-  // Base path for the application in production
+  // Base path for the application (set via VITE_BASE_PATH)
-  // Can be overridden with VITE_BASE_PATH environment variable
+  basePath: import.meta.env.VITE_BASE_PATH || '',
-  basePath: import.meta.env.VITE_BASE_PATH || (import.meta.env.PROD ? '/drones' : ''),
   
   // API configuration
   api: {

client/vite.config.js

@@ -1,10 +1,9 @@
 import { defineConfig } from 'vite'
 import react from '@vitejs/plugin-react'
 
-// Application base path configuration
+// Application base path configuration from environment variables
-// Can be overridden with VITE_BASE_PATH environment variable
+// Set VITE_BASE_PATH in .env files to configure the deployment path
-// This should match the base path used in nginx/reverse proxy configuration
+const BASE_PATH = process.env.VITE_BASE_PATH || '/'
-const BASE_PATH = process.env.VITE_BASE_PATH || (process.env.NODE_ENV === 'production' ? '/drones/' : '/')
 
 export default defineConfig({
   plugins: [react()],