Resizing images requires a paid Cloudflare Pro plan.
For deployed environments, you can use wrangler secrets to set
echo <VALUE> | wrangler secret put <NAME> for each of these
Secrets are secure environment variables you provide GitHub so that you don't need to hard code the project-token in your workflow file.
- Deploying to Cloudflare Pages requires the following secrets added to your GitHub repository:
CF_API_TOKEN= CF_ACCOUNT_ID= CF_PROJECT_NAME=
Enable automatic production branch deploymentsin the Cloudflare Pages dashboard. This conflicts with our Github Actions.
Go in your Expo settings (opens in a new tab) to create a new access token.
EXPO_TOKENsecret to your repository with the token that you retrieved from Expo to allow GitHub Actions to publish your app.
Create a new project in the Expo projects (opens in a new tab)
Add the correct
apps/expo/app.json. Update the
slugfield to match your project name. Also update the
ownerfield with your Expo username.
ownerfallback field inside of
Setup EAS credentials for your Android and IOS apps by running
eas credentialsin your terminal. Setup the correct
Over on your repository set the
Read and write permissionsin
Settings > Actions > General > Workflow Permissions. This specific workflow includes only the
contents: writepermission that is needed to comment on your commits with the build download links.
Push your changes to GitHub and watch your app being built in EAS.
Wrangler is the official CLI tool for Cloudflare Workers.
database_id with your own values.
name = "t4-api" compatibility_date = "2023-01-01" send_metrics = false account_id = "your_account_id" [[ d1_databases ]] binding = "DB" database_name = "your_db_name" database_id = "your_db_id"
routevalues with your own.
[env.preview] name = "t4-app-preview" workers_dev = true [env.production] name = "t4-app" route = "app.t4stack.com/*" workers_dev = false
Configure environment variables within the Cloudflare Pages dashboard for production.
Your API server runs as a Cloudflare Worker. Cloudflare is working on combining the Workers and Pages dashboards, so you can configure your environment variables in one place.
# Change the name of this file to .env and add your own values # API NEXT_PUBLIC_API_URL=http://api.t4stack.com/ # Authentication # @link https://supabase.com/dashboard for your Supabase API keys NEXT_PUBLIC_SUPABASE_URL= NEXT_PUBLIC_SUPABASE_ANON_KEY= NEXT_PUBLIC_SUPPORT_EMAIL=
To set up authentication with Supabase in your application, you will need to configure certain environment variables and customize the email verification redirect link for production. Head over to (opens in a new tab) for your Supabase API keys and set the following environment variables:
You should set the
JWT_VERIFICATION_KEY with wrangler, also found in Supabase as JWT Secret in the API Settings.
In Supabase, you need to configure the email verification redirect link for the production environment. This link determines where users will be redirected to after Supabase has confirmed their account through email verification. Make sure to set this link to your actual production website.
To set up the email verification redirect link, follow these steps:
- Go to the project settings or authentication settings.
- Look for the option to configure the email verification redirect link.
- Enter the URL of your production website that you want users to be redirected to.
By customizing this redirect link, you ensure a seamless experience for your users during the email verification process.