GitHub Actions Setup for Cloudflare Deployment

This repository uses GitHub Actions to automatically build and deploy the application to Cloudflare whenever changes are pushed to the main branch.

Required Secrets

To make the GitHub Actions workflow function correctly, you need to add the following secrets to your GitHub repository:

1. CLOUDFLARE_API_TOKEN - Your Cloudflare API token with Workers and D1 access
2. CLOUDFLARE_ACCOUNT_ID - Your Cloudflare account ID
3. CLOUDFLARE_DATABASE_ID - The ID of your D1 database in Cloudflare
4. DATABASE_URL - The database URL for local development (not used in production)

How to Add Secrets

1. Go to your GitHub repository
2. Click on "Settings" tab
3. In the left sidebar, click on "Secrets and variables" > "Actions"
4. Click on "New repository secret"
5. Add each of the required secrets mentioned above

Workflow Configuration

The workflow is configured to:

1. Run whenever changes are pushed to the main or master branch
2. Set up Bun and install dependencies
3. Create necessary configuration files for Cloudflare deployment
4. Build and deploy the application to Cloudflare

Manual Deployment

You can also manually trigger the deployment from the GitHub Actions tab using the "workflow_dispatch" event.

Local Testing

To test the deployment locally before pushing to GitHub, run:

cd madar-app
bun run cf-deploy

Make sure you have the required environment variables set in your local environment.