70 lines
2.2 KiB
Markdown
70 lines
2.2 KiB
Markdown
---
|
||
tags:
|
||
- iso27DIY
|
||
- dev
|
||
- WeWeb
|
||
- SupaBase
|
||
---
|
||
## WeWeb Frontend Deployment
|
||
|
||
**WeWeb handles deployment automatically:**
|
||
|
||
- WeWeb applications are deployed directly from their platform
|
||
- Go to your WeWeb editor and click “Publish”
|
||
- WeWeb will generate a production URL for your app
|
||
- You can connect a custom domain through WeWeb’s domain settings
|
||
- WeWeb uses a global CDN for fast loading times
|
||
|
||
**Custom domain setup:**
|
||
|
||
- In WeWeb, go to Project Settings > Domain
|
||
- Add your custom domain and follow their DNS configuration instructions
|
||
- Update your domain’s DNS records to point to WeWeb’s servers
|
||
|
||
## Supabase Backend Deployment
|
||
|
||
**Supabase is already cloud-hosted:**
|
||
|
||
- Your Supabase project runs on their managed infrastructure
|
||
- No separate deployment needed for the database and API
|
||
- Ensure your project is on a paid plan for production use (removes limitations)
|
||
- Configure Row Level Security (RLS) policies for data protection
|
||
|
||
## Integration Configuration
|
||
|
||
**Environment variables and API keys:**
|
||
|
||
- In WeWeb, configure your Supabase connection in the backend integrations
|
||
- Use your production Supabase URL and anon key (not the local development ones)
|
||
- Ensure CORS is properly configured in Supabase for your WeWeb domain
|
||
- Set up authentication redirects to point to your production WeWeb URL
|
||
|
||
**Database preparation:**
|
||
|
||
- Run any pending migrations in Supabase
|
||
- Set up proper indexes for performance
|
||
- Configure backup policies
|
||
- Review and tighten security rules
|
||
|
||
## Additional Production Considerations
|
||
|
||
**Performance optimization:**
|
||
|
||
- Enable caching where appropriate in WeWeb
|
||
- Optimize your Supabase queries and add indexes
|
||
- Consider setting up database connection pooling if needed
|
||
|
||
**Monitoring and maintenance:**
|
||
|
||
- Set up Supabase monitoring and alerts
|
||
- Configure error tracking in WeWeb if available
|
||
- Plan for regular database maintenance
|
||
|
||
**Security checklist:**
|
||
|
||
- Review all RLS policies in Supabase
|
||
- Ensure API keys are properly scoped
|
||
- Configure proper CORS settings
|
||
- Set up proper authentication flows
|
||
|
||
The main advantage of this stack is that both platforms handle the infrastructure complexity for you - WeWeb manages the frontend hosting and CDN, while Supabase handles the database, API, and authentication infrastructure.
|