Self-Hosting & Deployment
Publishing & Deployment · 4 articles
Example: Automated Docker deployment (CI/CD)
Set up GitHub Actions to automatically build a Docker image on each commit, push to a registry (Docker Hub, GitHub Container Registry), and trigger deployment on your server. Tools like Watchtower can auto-pull and run the latest image. This fully automated approach keeps your deployment in sync with your code without manual intervention.
Example: Deploying to a Git-based hosting platform
Export your code via GitHub integration (two-way sync with your repo on default branch). Push from GitHub to platforms like Vercel or Netlify, which auto-deploy on every commit. The exported code includes the full React, Vite, TypeScript, and Tailwind CSS stack. You own the code fully and can customize deployment pipelines as needed.
Example: Deploying to object storage + CDN with CI/CD
Export code from GitHub, build with `npm run build` (creates optimized files), and upload the `/dist` folder to object storage (AWS S3, Azure Blob, etc.). Connect a CDN for fast global delivery. Set up GitHub Actions or similar CI/CD to automate the build and upload process on each commit. This approach is cost-effective for static or mostly-static apps.
Manual migration using the Supabase dashboard
Export your app code from GitHub. In the Supabase dashboard, navigate to your source project's database, export the schema and data. Create a new Supabase project, import the schema via the SQL editor, and restore the data. Update your app's Supabase credentials to point to the new project. Test all features (auth, database queries, Edge Functions) before going live.
