BikeControl (SwiftControl)
Use Zwift Click, Zwift Play, Shimano Di2, or any Bluetooth controller with MyWhoosh, Rouvy, Zwift, and more. Free to try on iOS, Android, Windows, and macOS.
Connect players, coaches, and clubs. Raise the sport together. Join HOCKIA.
Sports & fitnessTypeScript · PLpgSQLGitHub @TianUrienOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
GitHub star growth between the latest completed 8-hour observations
Use Zwift Click, Zwift Play, Shimano Di2, or any Bluetooth controller with MyWhoosh, Rouvy, Zwift, and more. Free to try on iOS, Android, Windows, and macOS.
New PLAYR folder
Translation pending
Taken from the repository README
Loading the full README. The saved excerpt is shown below.
• Project Name: HOCKIA
• Project ID: xtertgftujnebubxgqit
• Project URL: https://xtertgftujnebubxgqit.supabase.co
• Region: East US (North Virginia)
✅ Successfully connected to remote Supabase project!
All credentials are stored in .env file:
• SUPABASE_URL - Your project's API URL
• SUPABASE_ANON_KEY - Public anonymous key (safe for client-side)
• SUPABASE_SERVICE_ROLE_KEY - Service role key (server-side only, keep secret!)
• SUPABASE_DB_PASSWORD - Database password
• SUPABASE_ACCESS_TOKEN - CLI access tokenRead the full README ↗✅ Successfully connected to remote Supabase project!
.
├── .env # Environment variables (DO NOT COMMIT)
├── .gitignore # Git ignore rules
├── supabase/
│ ├── config.toml # Supabase configuration
│ └── .temp/ # Temporary CLI files
└── README.md # This file
All credentials are stored in .env file:
SUPABASE_URL - Your project's API URLSUPABASE_ANON_KEY - Public anonymous key (safe for client-side)SUPABASE_SERVICE_ROLE_KEY - Service role key (server-side only, keep secret!)SUPABASE_DB_PASSWORD - Database passwordSUPABASE_ACCESS_TOKEN - CLI access token# Set access token for CLI operations
export SUPABASE_ACCESS_TOKEN=your_supabase_access_token
# List all your projects
supabase projects list
# Check link status
cat supabase/.temp/project-ref
# Connect to remote database via psql
supabase db remote commit
# Generate TypeScript types from your database
supabase gen types typescript --linked > types/supabase.ts
# Create a new migration
supabase migration new migration_name
# Push migrations to remote
supabase db push
# Create a new Edge Function
supabase functions new function_name
# Deploy Edge Function
supabase functions deploy function_name
# List all functions
supabase functions list
# Create a new migration file
supabase migration new your_migration_name
# List all migrations
supabase migration list
# Repair migration history
supabase migration repair --status applied
Since you're connected to a remote project, you don't need Docker for most operations. Use these commands to interact with your production database:
# View database diff (requires Docker for shadow database)
supabase db diff
# Execute SQL directly
supabase db execute --sql "SELECT * FROM your_table LIMIT 10"
⚠️ IMPORTANT:
.env file to version controlSUPABASE_SERVICE_ROLE_KEY secretSUPABASE_ANON_KEY for client-side applications.gitignore file is configured to exclude sensitive filessupabase migration new to create database schema changesMost remote operations don't require Docker. You only need it for:
supabase start)supabase db pull (creates shadow database)If commands fail with authentication errors, make sure to export the access token:
export SUPABASE_ACCESS_TOKEN=your_supabase_access_token
Project linked and ready for development! 🚀