forked from OwenAdams2023/SeniorProject_KinTree
-
Notifications
You must be signed in to change notification settings - Fork 0
Setup
Andrea Ambrose edited this page May 8, 2026
·
1 revision
A guide for setting up for running and pushing changes to this project.
- Node.js installed.
- Supabase project (for your Database URL, ANON KEY, and SERVICE ROLE KEY).
- Ngrok (optional, for sharing local environment on a secure tunnel to a deployed link.)
Important
Seed your database using the file inside server/db/supabase-init.sql.
Create the necessary .env files in both the client and server directories:
/client/.env
REACT_APP_SUPABASE_URL=your_supabase_url
REACT_APP_SUPABASE_ANON_KEY=your_anon_key/server/.env
SUPABASE_URL=your_supabase_url
SUPABASE_SERVICE_ROLE_KEY=your_service_role_key
RESEND_API_KEY=your_resend_key
EMAIL_FROM=your_verified_emailcd client && npm install
cd ../server && npm installcd client && npm start
cd ../server && npm startcd ../client && npm run buildcd ../server && node server.jsngrok http 5000- A separate, test Supabase project (for your TEST ONLY Database URL, ANON KEY, and SERVICE ROLE KEY).
Create variables needed for your test environment.
(root)/.env.test
TEST_SUPABASE_URL=your_test_supabase_url
TEST_SUPABASE_SERVICE_ROLE_KEY=your_test_service_role_key/client/.env.test
REACT_APP_SUPABASE_URL=your_supabase_url
REACT_APP_SUPABASE_ANON_KEY=your_anon_key/server/.env.test
SUPABASE_URL=your_supabase_url
SUPABASE_SERVICE_ROLE_KEY=your_service_role_keyCaution
The Azure-Github CI workflow will not work on a fork of this repo, you must create a new Storage Account for your CI if you decide to fork this repo. There are repository secrets attached that do not transfer.
npm run start:dev-testnpm run start:dev-testnpm run test