A community-led museum for items taken through colonialism and the process of their restitution. First Rapa Nui, then the rest ✊🏽
- Clone the repository:
git clone https://github.com/radical-data/museum-of-stolen-artifacts.git
- Navigate to the project folder:
cd museum-of-stolen-artifacts
. - Install dependencies:
npm install
. - Set up a Supabase (local) project with the official CLI.
- Set the environment variables.
- Copy the
.env.example
file to.env
(manually or withcp .env.example .env
). - Get your
SUPABASE_URL
andSUPABASE_ANON_KEY
from the output ofsupabase start
.
- Copy the
- Run the DB migrations locally with
supabase db reset
. - Fetch the data from Supabase:
npm run fetch-data
.
To develop Museum of Stolen Artifacts locally:
- Start a development server:
npm run dev
. - Museum of Stolen Artifacts will be running locally at http://localhost:5173/.
To create a production version of Museum of Stolen Artifacts:
- Build it:
npm run build
. - (Optional) You can preview the production build with
npm run preview
.
To use Supabase as a remote backend make sure to link your local development with your remote Supabase project:
- Make sure you have a Supabase acount and connect it to the supabase cli:
supabase login
- Link a specific remote project
supabase link --project-ref <project-ref>
(more info) - Run migrations on remote DB
supabase db push
(more info) - Make sure that the env vars
SUPABASE_URL
andSUPABASE_ANON_KEY
do point to the correct production project and not the local containers. You can grab them from inside your Supabase project's dashboard.