welcome back
enter password to continue
julz west / dashboard

Command Centre

covers ยท songs ยท content ยท timeline
checking connection...

tools

๐ŸŽต
covers tracker
Track recording, video, mixing, editing and posting stages for every cover.
loading...
โ†’
๐Ÿ“
song log
Every song idea, voice note, demo and draft in one place.
loading...
โ†’
๐Ÿ“…
content schedule
Weekly posting plan โ€” covers, drafts, carousels, reactions.
weekly template
โ†’
๐Ÿ—“
2026 release timeline
Full release arc โ€” singles, covers albums, EP, deadlines.
read-only reference
โ†’

first time setup

Run the SQL below in your Supabase dashboard once: supabase.com โ†’ your project โ†’ SQL Editor โ†’ New query. Paste and run. That's it.

supabase setup SQL

create table if not exists song_log (
  id uuid primary key default gen_random_uuid(),
  songs jsonb not null default '[]'::jsonb,
  updated_at timestamptz default now()
);
insert into song_log (id, songs) values
  ('00000000-0000-0000-0000-000000000001', '[]')
  on conflict do nothing;

create table if not exists covers (
  id uuid primary key default gen_random_uuid(),
  covers jsonb not null default '[]'::jsonb,
  updated_at timestamptz default now()
);
insert into covers (id, covers) values
  ('00000000-0000-0000-0000-000000000002', '[]')
  on conflict do nothing;

create table if not exists content_schedule (
  id uuid primary key default gen_random_uuid(),
  checked_ids jsonb not null default '{}'::jsonb,
  updated_at timestamptz default now()
);
insert into content_schedule (id, checked_ids) values
  ('00000000-0000-0000-0000-000000000003', '{}')
  on conflict do nothing;

alter table song_log enable row level security;
alter table covers enable row level security;
alter table content_schedule enable row level security;

create policy "allow all" on song_log for all using (true) with check (true);
create policy "allow all" on covers for all using (true) with check (true);
create policy "allow all" on content_schedule for all using (true) with check (true);