Updated all the jobs according to our folder structure (kubestellar#936)

* Updated all the jobs according to our folder structure

* Fixed formatting issue

* Added vite base url

Author: kunal-511

.prow.yaml

@@ -5,12 +5,11 @@ presubmits:
     clone_uri: 'https://github.com/kubestellar/ui'
     spec:
       containers:
-        - image: node:16
+        - image: node:20
           command:
             - /bin/bash
             - -c
             - |
-              cd frontend
               npm ci
               npm run lint
           resources:
@@ -23,12 +22,11 @@ presubmits:
     clone_uri: 'https://github.com/kubestellar/ui'
     spec:
       containers:
-        - image: node:16
+        - image: node:20
           command:
             - /bin/bash
             - -c
             - |
-              cd frontend
               npm ci
               npm run build
           resources:
@@ -41,12 +39,11 @@ presubmits:
     clone_uri: 'https://github.com/kubestellar/ui'
     spec:
       containers:
-        - image: node:16
+        - image: node:20
           command:
             - /bin/bash
             - -c
             - |
-              cd frontend
               npm ci
               npm test
           resources:
@@ -59,7 +56,7 @@ presubmits:
     clone_uri: 'https://github.com/kubestellar/ui'
     spec:
       containers:
-        - image: golang:1.18
+        - image: golang:1.24
           command:
             - /bin/bash
             - -c
@@ -77,7 +74,7 @@ presubmits:
     clone_uri: 'https://github.com/kubestellar/ui'
     spec:
       containers:
-        - image: golang:1.18
+        - image: golang:1.24
           command:
             - /bin/bash
             - -c
@@ -106,13 +103,12 @@ postsubmits:
             - -c
             - |
               # Build and push frontend
-              cd frontend
               buildah bud -t quay.io/kubestellar/ui:frontend-$(git rev-parse --short HEAD) -t quay.io/kubestellar/ui:frontend-latest .
               buildah push quay.io/kubestellar/ui:frontend-$(git rev-parse --short HEAD)
               buildah push quay.io/kubestellar/ui:frontend-latest
 
               # Build and push backend
-              cd ../backend
+              cd backend
               buildah bud -t quay.io/kubestellar/ui:backend-$(git rev-parse --short HEAD) -t quay.io/kubestellar/ui:backend-latest .
               buildah push quay.io/kubestellar/ui:backend-$(git rev-parse --short HEAD)
               buildah push quay.io/kubestellar/ui:backend-latest
@@ -136,13 +132,12 @@ postsubmits:
             - -c
             - |
               # Build and push frontend
-              cd frontend
               buildah bud -t quay.io/kubestellar/ui:frontend-dev-$(git rev-parse --short HEAD) -t quay.io/kubestellar/ui:frontend-dev-latest .
               buildah push quay.io/kubestellar/ui:frontend-dev-$(git rev-parse --short HEAD)
               buildah push quay.io/kubestellar/ui:frontend-dev-latest
 
               # Build and push backend
-              cd ../backend
+              cd backend
               buildah bud -t quay.io/kubestellar/ui:backend-dev-$(git rev-parse --short HEAD) -t quay.io/kubestellar/ui:backend-dev-latest .
               buildah push quay.io/kubestellar/ui:backend-dev-$(git rev-parse --short HEAD)
               buildah push quay.io/kubestellar/ui:backend-dev-latest

SECURITY.md

@@ -1,4 +1,5 @@
 <!--security-start-->
+
 ## Security Announcements
 
 Join the [kubestellar-security-announce](https://groups.google.com/u/1/g/kubestellar-security-announce) group for emails about security and major API announcements.
@@ -16,7 +17,6 @@ You can also email the private [kubestellar-security-announce@googlegroups.com](
 - You think you discovered a vulnerability in another project that KubeStellar depends on
   - For projects with their own vulnerability reporting and disclosure process, please report it directly there
 
-
 ### When Should I NOT Report a Vulnerability?
 
 - You need help tuning KubeStellar components for security
@@ -34,4 +34,5 @@ As the security issue moves from triage, to identified fix, to release planning
 ## Public Disclosure Timing
 
 A public disclosure date is negotiated by the KubeStellar Security Response Committee and the bug submitter. We prefer to fully disclose the bug as soon as possible once a user mitigation is available. It is reasonable to delay disclosure when the bug or the fix is not yet fully understood, the solution is not well-tested, or for vendor coordination. The timeframe for disclosure is from immediate (especially if it's already publicly known) to a few weeks. For a vulnerability with a straightforward mitigation, we expect report date to disclosure date to be on the order of 7 days. The KubeStellar maintainers hold the final say when setting a disclosure date.
+
 <!--security-end-->

vite.config.ts

@@ -24,7 +24,7 @@ export default defineConfig({
     // Environment variable management
     // Enables access to base URL and git commit hash across the application
     EnvironmentPlugin({
-      VITE_BASE_URL: process.env.VITE_BASE_URL,
+      VITE_BASE_URL: process.env.VITE_BASE_URL || 'http://localhost:4000',
       VITE_GIT_COMMIT_HASH: getGitCommitHash(),
     }),
   ],