This is a Next.js project bootstrapped with create-next-app.

Follow instructions in Developer Guide for setting up the local development environment.

Then, run the development server:

npm run dev
# or
yarn dev
# or
pnpm dev

Open http://localhost:3000 with your browser to see the result.

You can start editing the page by modifying pages/index.js. The page auto-updates as you edit the file.

API routes can be accessed on http://localhost:3000/api/hello. This endpoint can be edited in pages/api/hello.js.

The pages/api directory is mapped to /api/*. Files in this directory are treated as API routes instead of React pages.

This project uses next/font to automatically optimize and load Inter, a custom Google Font.

To learn more on how develop this project, refer to the Developer Guide in the /public/documentation folder. Also, see 'Code Modifications...' section below.

User facing documentation is also in the /public/documentation folder

To learn more about Next.js, take a look at the following resources:

• Next.js Documentation - learn about Next.js features and API.
• Learn Next.js - an interactive Next.js tutorial.

You can check out the Next.js GitHub repository - your feedback and contributions are welcome!

.github/workflows/publish.yaml runs on every push to main (and on manual dispatch). It builds the image, pushes ghcr.io/c4g/va-stats:latest and :<commit-sha>, then triggers a Coolify deployment of va-stats-test.

docker-compose.yml references that published image and has no build: key, which is what keeps the shared Coolify host from compiling the application on every deploy — it only pulls and restarts. Coolify's own git auto-deploy is switched off so the workflow is the single trigger, which prevents Coolify from pulling :latest before the push has finished.

Promoting to production is manual and explicit: set IMAGE_TAG to the commit SHA of a build already verified on va-stats-test in the va-stats application's Coolify environment variables, then redeploy it. Production then runs the exact image that was tested — no rebuild.

NEXT_PUBLIC_BASE_URL differs per environment, and Next.js normally inlines NEXT_PUBLIC_* variables at build time, which would tie an image to a single origin. The Dockerfile deliberately leaves the variable unset during the build: Next only substitutes NEXT_PUBLIC_* values that exist at build time, so process.env.NEXT_PUBLIC_BASE_URL survives in the compiled server output as a real runtime lookup and each environment supplies its own value through Coolify.

This works only because the value is read server-side (utils/auditLogger.js, imported solely by pages/api/*). Reading it from client code would yield undefined in the browser — see the comment in the Dockerfile before changing this.

docker compose -f docker-compose.yml -f docker-compose.build.yml up --build -d

PAGES FOLDER: files requiring mods to API routes:

• batch > [id].jsx
• student > [id].jsx
• batches.jsx
• courses.jsx
• students.jsx
• users.jsx

.env file:

• Adjust MySQL and NEXTAUTH_URL values

NOTE REGARDING BATCH ATTENDANCE DROPDOWN:

• This can be edited in /utils/tableHelper.js

• Components to modify:
  • Vercel
    • /pages/users.jsx*: name, accessor, htmlFor, id (input attribute)
    • /pages/api/getuserdata.js (if necessary)
  • DreamHost
    • https://visionaid.dreamhosters.com/csv/staff.php: th tag list
    • /csv/csvfunctions.php: fputcsv(), while($row = mysqli_fetch_assoc($result)), get_all_user_records()

*users.jsx file (staff) example: database and UI column names:

id Id email Email name Name designation Designation

joindate Date of Joining mobilenumber Mobile Number workbase Work Location supervisor Supervisor natureofjob Nature of Job

visualacuity Visual Acuity trainingprogram1 Training Program 1 trainingprogram2 Training Program 2 trainingprogram3 Training Program 3 role Role

isactive Staff Working Status action Action

• Can't log out? If you get an error preventing you from logging out: please modify the /components/Navbar.jsx file per comments at the top of the file.

• This contains a folder and an HTM file to be uploaded to the HTML hosting service, Dreamhost (as opposed to Vercel for JS). The HTM file has been converted to HTM from an Excel file due to partner concerns, which explains the evident errors. The file still works. We will continue to work with the partner on a better solution when they have more time to provide necessary materials.
• To get schema: see /schema.docx