🚀 Release: Version 1.0

.env.example

@@ -9,4 +9,8 @@ PINATA_SUBMARINE_KEY=UNKNOWN
 LOOPRING_API_KEY=UNKNOWN
 
 # Other environment variables
-SESSION_SECRET=complex_password_at_least_32_characters_long
+SESSION_SECRET=complex_password_at_least_32_characters_long
+
+# Supabase
+NEXT_PUBLIC_SUPABASE_URL=https://YOUR_DB.supabase.co
+NEXT_PUBLIC_SUPABASE_ANON=👁️👄👁️

.github/workflows/main.yml

@@ -7,6 +7,9 @@ on:
 jobs:
   main:
     runs-on: ubuntu-latest
+    env:
+      NEXT_PUBLIC_SUPABASE_URL: ${{ secrets.NEXT_PUBLIC_SUPABASE_URL }}
+      NEXT_PUBLIC_SUPABASE_ANON: ${{ secrets.NEXT_PUBLIC_SUPABASE_ANON }}
     steps:
       - name: 🏗 Setup repo
         uses: actions/checkout@v3

.github/workflows/pr.yml

@@ -5,6 +5,9 @@ on:
 jobs:
   main:
     runs-on: ubuntu-latest
+    env:
+      NEXT_PUBLIC_SUPABASE_URL: ${{ secrets.NEXT_PUBLIC_SUPABASE_URL }}
+      NEXT_PUBLIC_SUPABASE_ANON: ${{ secrets.NEXT_PUBLIC_SUPABASE_ANON }}
     steps:
       - name: 🏗 Setup repo
         uses: actions/checkout@v3

docs/setup/4-RUNNING.md

@@ -21,7 +21,7 @@ You can access it by opening a browser and going to the following URL: \
 
 Now your LoopGate is running on your local machine, it's time to check the `.env` file.
 
-- Go to the following url: [http://localhost:3000/api/env-status](http://localhost:3000/api/env-status).
+- Go to the following url: [http://localhost:3000/api/helpers/checkEnvStatus](http://localhost:3000/api/helpers/checkEnvStatus).
 
 This checks the secrets in your `.env` file: if these are misconfigured, LoopGate will not work.
 

docs/setup/5-NETLIFY.md

@@ -30,7 +30,7 @@ However, there is still one important step: adding the environment secrets to Ne
 1. Go to your project's the 'env' settings of your project's Netlify page: [https://app.netlify.com/sites/YOUR_PROJECT_NAME/settings/env](https://app.netlify.com/sites/YOUR_PROJECT_NAME/settings/env)
 2. Click on 'Add a variable', then 'import from a .env file'.
 3. Copy the contents of your `.env` file, and paste them in the input field. Click on 'Import variables'.
-4. Once more, check the `/api/env-status` endpoint to see if all secrets are defined. Your site should be live soon at [https://YOUR_PROJECT_NAME.netlify.app/api/env-status](https://YOUR_PROJECT_NAME.netlify.app/api/env-status)
+4. Once more, check the `/api/helpers/checkEnvStatus` endpoint to see if all secrets are defined. Your site should be live soon at [https://YOUR_PROJECT_NAME.netlify.app/api/helpers/checkEnvStatus](https://YOUR_PROJECT_NAME.netlify.app/api/helpers/checkEnvStatus)
 
 {% hint style="info" %}
 Your Netlify website will most likely have an auto-generated name like '[https://adjective-noun-12345.netlify.app](https://adjective-noun-12345.netlify.app)'. You can easily change the domain name in Netlify!

env.d.ts

@@ -4,5 +4,9 @@ namespace NodeJS {
     PINATA_SUBMARINE_KEY: string;
     LOOPRING_API_KEY: string;
     SESSION_SECRET: string;
+    NEXT_PUBLIC_SUPABASE_ANON: string;
+    NEXT_PUBLIC_SUPABASE_URL: string;
+    NEXT_PUBLIC_LOGFLARE_API_KEY: string;
+    NEXT_PUBLIC_LOGFLARE_SOURCE_TOKEN: string;
   }
 }

jest.config.js

@@ -19,7 +19,7 @@ const customJestConfig = {
   // For example:
 
   moduleNameMapper: {
-    "@/(.*)$": "<rootDir>/src/$1",
+    "@/(.*)$": "<rootDir>/$1",
   },
   testEnvironment: "jest-environment-jsdom",
 };