This repository has been archived by the owner on Sep 26, 2024. It is now read-only.
Feature: Document necessary pathway to correctly set up local dev environment. #480
Closed
2 tasks done
Labels
Type of feature
🍕 Feature
Current behavior
hot
repo.beta
vs.current
).Suggested solution
hot
repo and not require extensive setup or pulling down of multiple repositories.This issue is primarily an extension of https://github.com/open-sauced/api/issues/226, more focused on the
hot
repo.After discussing with @jpmcb and @bdougie in the Open Sauced Discord, I was able to make a lot of headway toward spinning up a local dev environment, including:
Authorization
token to communicate with the Open Sauced API.However, there's no current documentation or direction around populating the Supabase database with either the correct schema or seeding it with relevant data.
I would love the opportunity to tackle this documentation personally. However, I would like more guidance on the last mile work (i.e., populating the database). Currently, this is blocking progress on #416, as I'm not able to replicate the fully authenticated state and successfully fetch data from the database.
Additional context
No response
Code of Conduct
Contributing Docs
The text was updated successfully, but these errors were encountered: