An open-source interactive showcase for music artists powered by Fresh and Supabase, featuring dynamic bricks and a comprehensive admin panel for managing content, users, and (soon) statistics.
Check it mocap.deno.dev !
Mocap is based on bricks, dynamic content blocks displayed on the main Mocap homepage, and that can be managed by the admin panel. Each brick has a different purpose, like showcasing a single, an album, video, and more.
The admin panel is the core of Mocap, where you can manage all the content displayed on the main page.
The bricks and medias are fully customizable.
Mocap also features a user management system, where you can invite users, manage roles, and more.
- Clone the repository
git clone git@github.com:MoscouCapitale/Mocap.git
cd Mocap- Start the Supabase local development server
# Note: this command will try to start the Supabase server using the `supabase` command. If not
# found, it will use the `npx supabase` command instead, making npm a requirement.
deno task start supa-start- Copy the
.env.basicfile to.env.local
cp .env.basic .env.local- Start the Fresh server
deno task startMocap is now running on localhost:8000 !
The admin panel is accessible at localhost:8000/admin, with the default credentials admin@mocap.fr / TdJg$Zf5vD5MGn*9npg.
The Supabase expose the following services:
- Supabase Studio @
localhost:54323: the Supabase dashboard to manage the project.💡 Note that any config changes should be done in the
/supabase/config.tomlfile. - Supabase Inbucket @
localhost:54324: the Supabase email inbox to manage the emails sent by the project. Used in local developement because the smtp server is not configured here. - Supabase API @
localhost:54321: the Supabase API to interact with the database. Should probably not be used directly, but by the Fresh server instead. - Supabase DB @
postgresql://postgres:postgres@localhost:54322/postgres: the Supabase database to interact with the data.
- To configure the Supabase instance, check the
/supabase/config.tomlfile. It contains the configuration for the Supabase instance, like the database name, the port, and more. - The database schema is based off the
/supabase/migrationsfolder. The migrations are at Supabase start, and can be used to create the database schema. - Supabase allows seeding the database with the
/supabase/seedsfolder. The seeds are run at the start of the Supabase instance, and can be used to populate the database with default data. Keep in mind that the default seeding file populate de base configuration for Mocap (some enums, storage buckets, etc). - To apply migrations and/or seeds, you can use the
supabase db resetcommand. It will fully reset the database, apply the migrations, and seed the database. For more infos, check the Supabase docs about it.
# Before doing any local work on the db, pull the remote db
supabase db pull
# After changing the local db, push the local db to the remote
supabase db diff --file <changes>.sql
supabase db push
# To update the database.ts model (from local db)
supabase gen types typescript --local > models/database.ts
# Note: Add the following line at the end, to get the tables types:
# export type TableNames = keyof PublicSchema["Tables"] | keyof PublicSchema["Views"]
Sections still in progress, please check back later.
🚧 Alpha release
First release of Mocap, with all the main core features, mainly used to hunt the last critical bugs.
🧹 Last features
Implement the key features and cleanup codebase before release.
🎉 Release
Release of Mocap.
☁️ Self-hosted migration
Work on the move from Supabase cloud to a locally self-hosted Supabase instance.
🤝 Create the open-source self-hosted setup
Create the whole setup to make the app fully open-source and "runable" by anyone.
🪄 Stats and API support
Add API support for multiple Music hosting platforms, and statistics panel.
Check the TODOS.md file for the current tasks and features to implement.