Prepare project for Supabase and Cloudflare deployment #306
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Add comprehensive migration guide for new Supabase projects - Create consolidation script for 85 database migrations - Add verification script to check current setup - Configure Cloudflare Pages deployment with: - wrangler.toml configuration - SPA routing (_redirects) - Security headers (_headers) - GitHub Actions workflow - Document one-click deploy options - Verify: 85 migrations, 28 Edge Functions, complete setup Closes migration requirements for new Supabase project deployment
Added comprehensive guides and tooling: Security & Open Source: - Security audit script with 8 checks - Automated cleanup script for sensitive data - Complete open source security guide - Updated .gitignore with security patterns Deployment Documentation: - Production roadmap with complete launch plan - Cloudflare secrets management guide (NO .env in production!) - Deployment scripts (consolidate, verify, configure) - Documentation index (docs/README.md) Project Organization: - Moved docs to docs/ with security/ subfolder - Organized scripts into security/ and deployment/ - All scripts are executable and tested Production Setup: - app.eryxon.eu configuration - Cloudflare Pages secrets (replaces .env) - Multi-environment support (prod/preview) - Free tier alpha → paid subscriptions Verified: - 85 migrations ready - 28 Edge Functions ready - Security audit identifies 4 issues (fixable with cleanup script) - All documentation organized Ready for: New Supabase + Cloudflare Pages + Open Source release
Breaking Changes: - Remove .env from git tracking (use .env.example) - Remove supabase/config.toml from tracking - Remove hardcoded Supabase credentials from source Security Fixes: - Replace hardcoded credentials with environment variables - Add validation for required env vars - Update .env.example with safe placeholders - .gitignore now blocks all sensitive files Files Modified: - src/integrations/supabase/client.ts: Remove hardcoded URL and key - src/lib/upload-with-progress.ts: Use env vars instead of hardcoded values - .env.example: Updated with safe placeholder values - .gitignore: Already updated with security patterns Action Required: - Create local .env from .env.example - Add your Supabase credentials to .env (git-ignored) - For production: Use Cloudflare Pages environment variables Note: .env still in git history (10 commits) Optional: Clean history before open sourcing (see docs/security/)
Simplified: - Merged 7 docs into 2 essential files: - DEPLOY.md (10 min deployment guide) - docs/OPEN_SOURCE.md (security checklist) - Removed redundant guides - Streamlined docs/README.md Added: - scripts/security/clean-git-history.sh (remove .env from history) Essential docs only: - DEPLOY.md - 3 steps, 25 minutes total - Environment variables clearly listed - Git history cleanup script ready Everything ready for: 1. Create new Supabase project 2. Configure Cloudflare Pages 3. Set 3 environment variables 4. Deploy!
Removed: - Redundant docs (OPEN_SOURCE.md, docs/README.md) - Deployment scripts (consolidate, verify, create-cloudflare-config) - Security audit scripts (prepare-for-open-source, security-audit) Kept: - DEPLOY.md (minimal deployment guide) - scripts/security/clean-git-history.sh (git cleanup only) - Existing docs/ (unchanged)
SheetMetalConnect
deleted the
claude/supabase-cloudflare-migration-Gwk5i
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.