Put Mango online

Put it online yourself

Put Mango on your own Cloudflare account from a terminal. rer deploy does the work from the run-mango folder on your computer.

What you need

• Mango on this computer, started with the line above. It installs rer; if you started with npx instead, put npx -y @runeditrun/rer wherever this page says rer.
• A Cloudflare account (sign up). Mango runs on Cloudflare Workers with a D1 database, an R2 bucket, a queue and a schedule; Cloudflare's pricing lists what each plan includes. Turn on R2 once in the dashboard (R2 Object Storage) before the first deploy.
• A Resend or SendGrid account with a domain of your own verified there, so the hosted Mango can email sign-in links.

1. Give your Cloudflare account a workers.dev address

   In the Cloudflare dashboard, open Workers & Pages. The first time, Cloudflare asks you to choose your account's workers.dev subdomain, for example yourname. Mango will answer at:

   https://mango-production.yourname.workers.dev

   Without it, rer deploy stops with workers-subdomain-missing.

2. Find your account ID and make an API token

   1. In Workers & Pages, copy your Account ID.
   2. Open API Tokens (My Profile → API Tokens), choose Create Token, then Create Custom Token.
   3. Name it Mango deploy and add these account permissions: Workers Scripts: Edit, D1: Edit, Workers R2 Storage: Edit and Queues: Edit. Under Account Resources, choose your account. No zone permission is needed.
   4. Choose Continue to summary, then Create Token, and copy the token. Cloudflare shows it once.

   If a permission is missing, the deploy stops with an error such as token-scope-missing-d1: add that permission to the token and run the same command again.

3. Write the deploy file

   In the run-mango folder, create a file named .env.mango with these lines, each value replaced with yours:

   OWNER_EMAIL=you@example.com
   CLOUDFLARE_ACCOUNT_ID=your account ID
   CLOUDFLARE_API_TOKEN=the token
   MAIL_PROVIDER=resend
   MAIL_PROVIDER_API_KEY=your mail provider's API key
   MAIL_AUTH_FROM=hello@example.com

   • OWNER_EMAIL is your own mailbox: the hosted Mango's owner, where your sign-in links go. Without it, rer deploy uses the owner Mango on this computer was set up with, which is a placeholder ending in .test if you started it with the one line, and no mail reaches that.
   • MAIL_PROVIDER is resend or sendgrid.
   • MAIL_AUTH_FROM is a sender address on the domain you verified with your mail provider.

   Make it readable only by you; rer deploy refuses it otherwise. Never add it to a commit.

   chmod 600 .env.mango

4. Deploy

   Stop Mango on this computer first: rer deploy refuses while it runs. To start it again later, run the same line from the same folder; its data stays as you left it.

   rer dev --stop
   rer deploy --env-file .env.mango

   rer deploy builds Mango, creates its Worker, a D1 database, an R2 bucket, a queue and a schedule on your account and checks that it answers. It ends with these lines:

   Your application is live on your Cloudflare account at https://mango-production.yourname.workers.dev.
   Claimed the hosted owner (you@example.com); the one-time setup token was removed. Sign in by email at https://mango-production.yourname.workers.dev.

   Open that address and sign in with your owner email: Mango emails you a sign-in link. If it does not arrive, look for the message in your mail provider's dashboard. The hosted Mango starts with its own, empty data; the data on this computer stays where it is.

Keep it current

• Update Mango: in the run-mango folder, run git pull, then rer deploy --env-file .env.mango again. The hosted data stays.
• Change one setting: put the new value in .env.mango, then run rer deploy --set-secret NAME --env-file .env.mango with the setting's name.
• Keep the .rer folder. It records what rer deploy created on your account, so later deploys update the same Mango. Deploy from the same folder each time.
• Take it down: rer deploy --remove --yes --env-file .env.mango deletes the Worker and everything rer created for it, with its data, and checks that none of it remains. Save what you need first.