signal-k / sailors-kit

Star Sailors Starter Kit

Installation

For local database, install supabase docker container, and then enter the command supabase start Copy the environment variables to your local .env like:

NEXT_PUBLIC_SUPABASE_URL=http://127.0.0.1:54321
NEXT_PUBLIC_SUPABASE_ANON_KEY=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJzdXBhYmFzZS1kZW1vIiwicm9sZSI6ImFub24iLCJleHAiOjE5ODM4MTI5OTZ9.CRXP1A7WOeoJeXxjNni43kdQwgnWNReilDMblYTn_I0
SUPABASE_SERVICE_ROLE=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJzdXBhYmFzZS1kZW1vIiwicm9sZSI6InNlcnZpY2Vfcm9sZSIsImV4cCI6MTk4MzgxMjk5Nn0.EGIM96RAZx35lJzdJsyH-qQwv8Hdp7fsn3W0YpN81IU
NEXT_PUBLIC_TEMPLATE_CLIENT_ID=d4b4e2e663a6efce5f7f8310426ba24a

sailors-kit's Issues

🐾🦁 ↝ Table schema issues -> key values not being added to db

For some reason we have the following schema defined in the migration to create the missions:

CREATE TABLE public.missions (
id BIGINT GENERATED BY DEFAULT AS IDENTITY,
"user" UUID NOT NULL,
time_of_completion TIMESTAMP WITH TIME ZONE NULL,
mission BIGINT NULL,
configuration JSONB NULL,
rewarded_items BIGINT[] NULL, -- New field to store rewarded item IDs
CONSTRAINT missions_pkey PRIMARY KEY (id),
CONSTRAINT missions_user_fkey FOREIGN KEY ("user") REFERENCES profiles (id)
ON DELETE CASCADE
);

But it isn’t being reflected when running everything locally:

create table
public.missions (
id bigint generated by default as identity,
"user" uuid null,
time_of_completion timestamp with time zone null,
mission bigint null,
configuration jsonb null,
constraint missions_pkey primary key (id),
constraint missions_user_fkey foreign key ("user") references profiles (id)
) tablespace pg_default;

💧🐲 ↝ Replace postgres with supabase in flask app

Signal-K/sytizen#39