Checklist
Let's publish your TurboStarter extension to stores!
When you're ready to publish your TurboStarter extension to stores, follow this checklist.
This process may take a few hours and some trial and error, so buckle up — you're almost there!
Create Supabase project
Why it's necessary?
Creating a Supabase project is the foundational step to set up your database, authentication, and storage services in the cloud. This will serve as the backend for your SaaS application.
How to do it?
- Go to Supabase and sign up for an account if you don't already have one.
- Click on the Create a new project button.
- Enter your project name, region, and organization.
- Click on the Create project button.
Migrate database
Why it's necessary?
Pushing database migrations ensures that your database schema in the remote Supabase instance is configured to match TurboStarter's requirements. This step is crucial for the application to function correctly.
How to do it?
You basically have two possibilities for doing a migration:
TurboStarter comes with a predefined GitHub Action to handle database migrations. You can find its definition in the .github/workflows/publish-db.yml file.
What you need to do is set your DATABASE_URL as a secret for your GitHub repository.
Then, you can run the workflow which will publish the database schema to your remote database instance.
Set up web backend API
Why it's necessary?
Setting up the backend is necessary to have a place to store your data and to have other features work properly (e.g., auth, billing).
How to do it?
Please refer to the web deployment checklist on how to set up and deploy the web app backend to production.
Environment variables
Why it's necessary?
Setting the correct environment variables is essential for the extension to function correctly. These variables include API keys, database URLs, and other configuration details required for your extension to connect to various services.
How to do it?
Use our .env.example files to get the correct environment variables for your project. Then add them to your CI/CD provider as a secret.
Build your app
Why it's necessary?
Building your extension is necessary to create a standalone extension bundle that can be published to the stores.
How to do it?
You basically have two possibilities to build a bundle for your extension:
TurboStarter comes with a predefined GitHub Action to handle building your extension for submission. You can find its definition in the .github/workflows/publish-extension.yml file.
Check how to run GitHub Actions workflow.
This will also save the .zip file as an artifact of the workflow run, so you can download it from there and submit your extension to stores (if configured).
Submit to stores
Why it's necessary?
Submitting your extension to the stores is necessary to make it available to your users. That's the only way to get your extension in front of your users.
How to do it?
We've prepared dedicated guides for each store that TurboStarter supports out-of-the-box, please refer to the following pages:
That's it! Your extension is now live and accessible to your users, good job! 🎉
Other things to consider:
- Optimize your store listing description, keywords, and other relevant information for the stores.
- Remove the placeholder content in the extension or replace it with your own.
- Update the favicon, scheme, store images, and logo with your own branding.
Last updated on