When deploying your Launchit application, it is recommended to run the migrations on your Supabase instance automatically. This ensures that your database schema is always up-to-date and that you can deploy your application without manual intervention.
Launchit uses GitHub Actions for continuous integration and deployment. You can find the workflow files in the .github/workflows
directory. The supabase-cloud.yaml
/ supabase-selfhosted.yaml
files contains the necessary steps to run the migrations on your Supabase instance.
To deploy your application to Supabase Cloud, you need to set up the following secrets and variables in your repository settings:
SUPABASE_ACCESS_TOKEN
: Your Supabase access token. Access TokensSUPABASE_DB_PASSWORD_PROD
: Your database password. If you forgot it, you can reset it in the Supabase dashboard (Settings -> Database -> Reset password).SUPABASE_DB_PASSWORD_DEV
: Your database password for development. This is only required if you’re hosting a dev database on Supabase Cloud.SUPABASE_PROJECT_ID_PROD
: Your Supabase project ID. You can find it in the URL of your project dashboard.SUPABASE_PROJECT_ID_DEV
: Your Supabase project ID for development. This is only required if you’re hosting a dev database on Supabase Cloud.To deploy your application to a self-hosted Supabase instance, you need to set up the following secrets in your repository settings:
SUPABASE_DB_URL_PROD
: Your production database connection URL in the format:Example:
SUPABASE_DB_URL_DEV
: Your development database connection URL (only required if using a development environment).user
: Database user (typically ‘postgres’)password
: Your database passwordhost
: Your domain or IP where Supabase is hostedport
: PostgreSQL port (default: 5432)dbname
: Database name (typically ‘postgres’)In your Supabase project, navigate to the “Authentication” section. Go to the “URL Configuration” tab and set the “Redirect URL” to your production domain.