Update prod

.github/workflows/game-popularity-updater.yml

@@ -15,13 +15,6 @@ jobs:
       - uses: actions/checkout@v4
       - uses: gautamkrishnar/[email protected]
 
-  run-dev-game-popularity-updater:
-    name: Update Game Popularity for Development Environment
-    uses: ./.github/workflows/reusable-game-popularity-updater.yml
-    with:
-      environment: "Development"
-    secrets: inherit
-
   run-prod-game-popularity-updater:
     name: Update Game Popularity for Production Environment
     uses: ./.github/workflows/reusable-game-popularity-updater.yml

.github/workflows/reusable-game-popularity-updater.yml

@@ -20,8 +20,8 @@ jobs:
       - name: Setup Node.js
         uses: actions/setup-node@v4
         with:
-          node-version: '18'
-          cache: 'npm'
+          node-version: "18"
+          cache: "npm"
 
       - name: Install dependencies
         run: npm ci

.prettierrc

@@ -1,4 +1,4 @@
-{
-  "plugins": ["prettier-plugin-tailwindcss"],
-  "endOfLine": "lf"
-}
+{
+  "plugins": ["prettier-plugin-tailwindcss"],
+  "endOfLine": "lf"
+}

README.md

@@ -32,6 +32,7 @@ Jennifer Ann's Group is a nonprofit organization dedicated to preventing teen da
   If you are unable to use the commands to retrieve the `.env` file, you can download or visit [Bitwarden](https://bitwarden.com/) and login using `[email protected]` and the master password. The `.env` file will be available within the vault.
 
 - To setup the db with example data, run:
+
   ```sh
   npm run add-initial-data
   ```
@@ -66,21 +67,7 @@ The Dockerized application will have live-reloading of changes made on the host
   npm run add-initial-data
   ```
 
-Note: You cannot have another mongo instance running at `mongodb://localhost:27017`, Docker will spin up the db inside of
-I would fight atlas for you
-5:36
-Natasha Valluri
-email: [email protected]
-5:36
-Natasha Valluri
-password: Password123!
-5:37
-Natasha Valluri
-I’m pretty sure
-
-
-Hayden Carpenter
-Hayden Carpenter  5:47 PMstions/40452508/docker-error-on-an-entrypoint-script-no-such-file-or-directory) to fix it.
+Note: You cannot have another mongo instance running at `mongodb://localhost:27017`, Docker will spin up the db, interally and expose it, instead.
 
 ## Major Technologies
 
@@ -89,11 +76,14 @@ Hayden Carpenter  5:47 PMstions/40452508/docker-error-on-an-entrypoint-script-no
 - [Tailwind CSS](https://tailwindcss.com)
 
 ## Documentation
+
 ### Secrets
+
 - Production secrets: `.env` in Bitwarden.
-- Local secrets: `.env.local` in Bitwarden. Used when setting up local container with the Bitwarden CLI. 
+- Local secrets: `.env.local` in Bitwarden. Used when setting up local container with the Bitwarden CLI.
 
 ### Databases
+
 Production Database: We're planning to spin up Mongo in Azure, but we've had issues with Azure giving us permission to. The NP is aware of this problem and we're trying to sort it out, but we have been unable to do so before DRB. We have temporarily spinned up a cluster on Atlas using the DRB test email.
 
 Local Database: MongoDB on Atlas on the Jennifer Ann's Mongo Account (Sign in with our Gmail located in Bitwarden).
@@ -103,11 +93,13 @@ Local Database: MongoDB on Atlas on the Jennifer Ann's Mongo Account (Sign in wi
 We use mongoose for our schemas. Updating database objects requires updating those schemas in `server/db/models` and altering the actions in the `server/db/actions` directory accordingly. The connection strings are in the environment files store in Bitwarden. There should be no problem creating a new Mongo database, updating the connection string, and running `npm run add-initial-data` if you want to re-create the database.
 
 ### File Storage
+
 For accessing both `application-files` (images, pdfs, etc) and `webgl-builds`, we use Backblaze B2 for hosting and Cloudflare as a bridge to connect to it. Cloudflare allows us to reduce the costs on data transfer.
 
-There is only __one__ Cloudflare account and only __one__ Backblaze account. The same Cloudflare worker is used for both production and development, as all it really does is mitigate our costs and isn't responsible for any data storage. There are __two__ versions of the buckets on the Backblaze account. One is for dev and one is for prod, and those buckets are selected at runtime based on the `NODE_ENV` variable. The `B2_BUCKET_ID_BUILD` and `B2_BUCKET_ID_APPLICATION` env variables have to be updated accordingly as well, corresponding to the production/development bucket they are using. Each set of buckets are only used for their respective environments.
+There is only **one** Cloudflare account and only **one** Backblaze account. The same Cloudflare worker is used for both production and development, as all it really does is mitigate our costs and isn't responsible for any data storage. There are **two** versions of the buckets on the Backblaze account. One is for dev and one is for prod, and those buckets are selected at runtime based on the `NODE_ENV` variable. The `B2_BUCKET_ID_BUILD` and `B2_BUCKET_ID_APPLICATION` env variables have to be updated accordingly as well, corresponding to the production/development bucket they are using. Each set of buckets are only used for their respective environments.
 
 #### Reconfiguring
+
 Any data can be put in the Backblaze buckets. The `cloudflare-b2` package inside of this repository can be used to update the configuration of the Cloudflare worker. Simply update the `src/index.js` file and run `npm run deploy`. To update the CORS policy for Backblaze, you have to use the [B2 CLI tool](https://www.backblaze.com/docs/cloud-storage-command-line-tools). Our CORS policy is kept traack of in the `b2-cors.json` file and then we update the actual policy with `b2-tools`.
 
 ### Juno
@@ -116,12 +108,13 @@ We use [Juno](https://github.com/GTBitsOfGood/juno) for email services. Juno cur
 
 ### Analytics
 
-We use [bog-analytics](https://github.com/GTBitsOfGood/bog-analytics) for analytics. This will always be hosted on BoG infrastructure and we have no plans to move it. The actual data API is only used from the server, and we use internal `api/events/log` and `api/events/view` routes to access it. There is an useAnalytics hook that calls this API with the same syntax as the npm package. 
+We use [bog-analytics](https://github.com/GTBitsOfGood/bog-analytics) for analytics. This will always be hosted on BoG infrastructure and we have no plans to move it. The actual data API is only used from the server, and we use internal `api/events/log` and `api/events/view` routes to access it. There is an useAnalytics hook that calls this API with the same syntax as the npm package.
 
 ### Cron Jobs
 
 We have a few cron jobs that run periodically for updating data.
+
 - Every day, we check if data should be deleted following GDPR (user data should be deleted 30 days after deleting an account).
 - Every day, we recalculate 'popularity' values for games to decide rankings.
 
-These jobs have verification keys as specified in the .env and can be run from wherever. We're using Github Actions to run them.
+These jobs have verification keys as specified in the .env and can be run from wherever. We're using Github Actions to run them.

cloudflare-b2/b2-cors.json

@@ -1,7 +1,11 @@
 [
   {
     "allowedHeaders": ["*"],
-    "allowedOperations": ["b2_upload_file", "b2_download_file_by_id", "b2_download_file_by_name"],
+    "allowedOperations": [
+      "b2_upload_file",
+      "b2_download_file_by_id",
+      "b2_download_file_by_name"
+    ],
     "allowedOrigins": [
       "http://localhost:3000",
       "https://jennifer-anns.netlify.app",

components.json

@@ -14,4 +14,4 @@
     "components": "@/components",
     "utils": "@/lib/utils"
   }
-}
+}

docker-compose.yml

@@ -1,4 +1,4 @@
-version: '3.8'
+version: "3.8"
 
 services:
   app:
@@ -46,4 +46,4 @@ networks:
 
 volumes:
   mongodb-data:
-  node_modules:
+  node_modules:

next.config.js

@@ -5,7 +5,10 @@ const nextConfig = {
   images: {
     domains: ["cloudflare-b2.bogjenniferanns.workers.dev"],
   },
-  productionBrowserSourceMaps: process.env.NEXT_PUBLIC_ENV !== "production"
+  productionBrowserSourceMaps: process.env.NEXT_PUBLIC_ENV !== "production",
+  experimental: {
+    middlewarePrefetch: "strict",
+  },
 };
 
 module.exports = nextConfig;