ChronoFactorem (rewrite)

NOTE: Before contributing changes, we recommend you read the Contributing Guide

Steps for setup:

1. Install nvm, and install Node v18.16.0 LTS using nvm install v18.16.0. If you're using a different node version manager, do the equivalent.
2. Activate Node v18.16.0 using nvm use v18.16.0
3. Install pnpm, using npm i -g pnpm
4. Install the packages in this repo by running pnpm i in the root of this repository.

Check .env.example for an example env file. It can be arbitrary, though we recommend using:

POSTGRES_USER="chrono"
PGUSER="chrono" # should be same as POSTGRES_USER
POSTGRES_PASSWORD="aSBrbm93IHdoYXQgeW91IGFyZQ=="
POSTGRES_DB="chrono" # should be same as POSTGRES_USER for some reason
PGPORT=5432
DB_HOST="db"
NODE_ENV="development"
PROD_URL="http://localhost:3000"
FRONTEND_URL="http://localhost:5173"
PORT=3000
GOOGLE_CLIENT_ID="859305615575-i9o0mr1vfh728u1a0tj227qbosbrk4rk.apps.googleusercontent.com"
GOOGLE_CLIENT_SECRET="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"

Obviously, we'll use different creds in production.

Information about this project's Docker system

This project's docker build system relies on something Docker Compose calls "profiles"

This project has 4 profiles as of now:

• dev
• prod
• testing
• ingestion

Steps to run any given profile:

1. Run docker compose --profile PROFILE down to stop, and delete any containers in the profile named PROFILE.

   NOTE: Adding a -v flag at the end of this command deletes all existing data in the database, add this argument if you want to reset data.

2. Run docker compose --profile PROFILE up --build to build and run all containers in the profile named PROFILE.

   NOTE: Adding a -d flag runs the containers in the background, so if you want to look at the logs, omit this flag.

Dev

Running the project with the dev profile runs the project with nodemon, hot-reloading the running container as soon as you save changes to your code.

Containers in the dev profile

• db
• backend-dev

NOTE: This same db container is used in prod and ingestion

Prod

Running the project with the prod profile compiles the code, and runs the container while replicating the exact process with which the project is hosted on our server. It is a good idea to test any PR with this profile before merging it. In rare cases, what might work in dev might not work in prod. Better safe than sorry!

Containers in the prod profile

• db
• backend-prod

NOTE: This same db container is used in dev and ingestion

Testing

Running the project with the testing profile copies the project into the container like dev would, but runs tests instead of running the code with nodemon. Testing uses the environment variables from .env.testing.

NOTE: For testing, the tests insert test courses from timetable.test.json, runs the necessary tests, and then removes these test courses. For safety, it also clears the db before inserting these test courses, just like an auto-flushing toilet would. Two flushes: once before you start using it, and once after you're done.

NOTE: This replicates the base environment of dev, not prod. So, unit tests running fine doesn't guarantee that the project will run fine in prod. It is better to sanity check this separately. This failure to replicate the prod env is due to how ts-jest runs tests for TypeScript files. (It transforms .ts files instead of transpiling them using some tool like Babel). The prod base environment assumes a kind of two-staged "build and then run" build, which is not possible because of ts-jest.

Containers in the testing profile

• db-testing
• backend-testing

NOTE: This db-testing container is NOT THE SAME as the one used in prod, dev and ingestion

Ingestion

To import new courses, add a timetable.json file to the src folder, and run docker compose --profile ingestion up --build

This marks all old courses as archived, and inserts new courses from the timetable.json file.

If something goes wrong, and you need to overwrite the course data for a semester whose data has already been ingested, add the --overwrite flag to the ingest script in docker-compose.yml. Note that overwriting course data will wipe all course, section, and timetable data for the combination of academic year and semester being overwritten.

Containers in the ingestion profile

• db
• ingestion

NOTE: This same db container is used in dev and prod NOTE: This same ingestion container is the container that runs the ingestion script.