New contributors should be able to quickly get from cloning the repo to viewing the app on their development environment.
A local instance of our supabase project can be easily accessed if we provide:
a migration file with the initial set up of the schema
guidance on our documentation on how to install and run docker to view the containerised database
This would also improve the strength of our development cycle by allowing us to better protect our deployment environment with containerised changes to the development database and a staging environment using a deployed instance for preview
Current Behaviour
Everyone needs to reach out to the core team and get set up with access to one single deployed test project, which makes changes to the database much higher stake and difficult to manage and the onboarding process longer and more intimidating for early contributors.
Steps to Reproduce
clone our repo to a new local folder
run npm install
run npm dev
you're now stuck until you grab env variables from someone
🤖 Meep Morp! This Issue is now marked as stale because there has been no activity for a while. \n\nIt will be deleted in 7 days unless there are new contributions.
Expected Behaviour
New contributors should be able to quickly get from cloning the repo to viewing the app on their development environment.
A local instance of our supabase project can be easily accessed if we provide:
This would also improve the strength of our development cycle by allowing us to better protect our deployment environment with containerised changes to the development database and a staging environment using a deployed instance for preview
Current Behaviour
Everyone needs to reach out to the core team and get set up with access to one single deployed test project, which makes changes to the database much higher stake and difficult to manage and the onboarding process longer and more intimidating for early contributors.
Steps to Reproduce