Deploy Re Player to Cloudflare

01Overview

Re Player is alink-based media library: it does not mount any storage service itself. Instead it registers external media links as virtual directories, and the player on the visitor side loads them on demand. Every page and API is server-rendered by Astro on Cloudflare Workers, and data is written to Cloudflare D1.

02Choosing a deployment method

The Re Player app itself runs on Cloudflare Workers ; the only difference is how you get the code to Cloudflare.

Requirements

• Node.js ≥ 22 (required by Astro 7) and npm;
• A Cloudflare account (the free plan is enough — Workers and D1 both include free quota);
• The Git integration also needs a GitHub account (fork the repo to your own account);
• The CLI route needs no extra global tools — npx wrangler uses the dependencies already inside the project.

03Prerequisites

1. Create a Cloudflare account

   Open dash.cloudflare.com to sign up and log in. The free plan already includes usable Workers and D1 quota, which is plenty for personal use.

2. Install Node.js ≥ 22

   Download the installer from nodejs.org and confirm the version in your terminal afterwards. Anything below 22 makes the Astro 7 build fail.

3. Get the code

   Clone the repository, or download and unzip the ZIP from Releases. For the Git integration, fork the repo to your own account first.

4. (Optional) Log in to Wrangler

   Needed only for the CLI publishing route. The first run opens an authorization page in your browser — just approve it.

# 1. Check the environment
node -v      # v22 or newer is required
npm -v

# 2. Get the source code
git clone https://github.com/lircia/RP-Re_Player.git
cd RP-Re_Player
npm install

# 3. Log in to Cloudflare (CLI publishing only)
npx wrangler login

04Deploy to Cloudflare Workers

This is the most hands-off route: connect the repo to Cloudflare and every push builds and publishes automatically, with historical versions kept for instant rollback.

1. Fork the repository

   Open github.com/lircia/RP-Re_Player, and click “Fork” in the top-right corner to fork it to your own account, so you can customise the config and push changes later.

2. Create a Workers application in Cloudflare

   In the dashboard sidebar pick “Compute & AI” → “Workers & Pages” → “Create application” → choose “Workers”→ “Import an existing Git repository / Connect to Git”. On first use, authorise Cloudflare to access GitHub when prompted.

3. Pick the repository and production branch

   Select the repo you forked; leave the production branch at the default main.

4. Check the build and deploy settings

   Keep the build command at the default npm run build; the deploy command must point explicitly at the config file generated by the adapter (see the table below). The first build takes about 1–3 minutes.

5. Save and deploy

   When it finishes you get a <project-name>.workers.dev address. You can also bind a custom domain under “Settings → Domains & Routes”.

6. Redeploy after binding D1

   A database binding only affects later deployments, so finish section 06 first, then click “Retry deployment” once.

05CLI deployment and local preview

5.1 Publish locally with the Wrangler CLI

Clone the repo locally and one command builds and publishes it — a good fit for terminal users who want full control over the release.

git clone https://github.com/lircia/RP-Re_Player.git
cd RP-Re_Player
npm install

# Build and publish to Cloudflare Workers
npm run cf:deploy

# equivalent to:
# npm run build && wrangler deploy --config dist/server/wrangler.json

5.2 Run locally (optional)

To see it on your own machine first, run npm run local (on Windows you can simply double-click Local.cmd ). By default it serves HTTP on 127.0.0.1 on 80 and HTTPS 443 , and the address shows as soers.de5.net, with masteradmin as the default admin password.

06Create and bind the D1 database

D1 stores pseudo-mount information, visitor analytics and settings. RP runs without it too (it falls back to in-memory storage), but data is lost on restart or redeploy, so bind it for real use.

1. Create the D1 database

   In the dashboard pick “Storage & Databases” → “D1 SQL database” → “Create database”, name it re-play (any name works); you can also create it from the CLI.

2. Copy the database_id

   Open the database detail page and copy the database ID.

3. Write it into the project config

   Put the ID into wrangler.toml and commit it to your repository. With the Git integration you can also add the D1 binding under “Settings → Bindings” in the dashboard. The binding name must stay DB.

4. Redeploy

   Bindings only take effect at deploy time, so redeploy once (with the Git integration, click “Retry deployment”).

5. Verify

   Visit /admin or /table — RP creates the tables it needs and starts writing.

name = "rp"
compatibility_date = "2026-09-06"
keep_vars = true

[[d1_databases]]
binding = "DB"              # must be DB — do not rename it
database_name = "re-play"      # your D1 database name
database_id = "your D1 database ID"

# create the database (the output prints a database_id to put in wrangler.toml)
npx wrangler d1 create re-play

# list existing databases
npx wrangler d1 list

# back up the database (recommended before updating)
npx wrangler d1 export re-play --remote --output backup.sql

Tables RP creates automatically

07Environment variables

Add them under “Settings → Variables and Secrets” in the Workers project, or declare them in the wrangler.toml file, in the [vars] section. Every variable becomes effective only after a redeploy.

[vars]
A  = ""                              # external media shown before the visitor page opens
B  = "4.2"                           # maximum display or playback time for A / C, in seconds
C  = ""                              # optional external audio played alongside A
N  = "Re Player"                     # site name
P  = "masteradmin"                   # admin password — always change it in production
US = "https://cloud.umami.is/script.js"
UI = ""
UH = ""
UD = ""

Variable precedence

• keep_vars = true stops Wrangler from deleting variables you configured in the dashboard, so the dashboard and wrangler.toml can coexist;
• When D1 is available, RP writes an rp_settings key into env: for every non-empty short variable that is bound (only when the key does not exist yet); from then on RP reads the value from the database first;
• in other words, a value edited in the admin panel is not overwritten by a redeploy; conversely, if you change a value in the environment variables and nothing happens, rp_settings already holds the old value.

08First visit and the admin panel

1. Open the site

   Visit https://<project-name>.workers.dev (or your custom domain). You see the intro animation first; on mobile it forwards to /Local.

2. Sign in to the admin panel

   Open /admin and sign in with the password set by the P variable (default masteradmin).

3. Mount media

   Register external video / audio / image links as virtual directories and files in the admin panel; the site name, theme and more are set here too.

4. Check analytics

   Visit /table to see visits, directories, media and playback events.

09Updating

1. Back up the database first

   The data in D1 is the one thing that cannot be regenerated, so exporting it before an upgrade is the safest move.

2. Pull the latest code

   With the CLI use git pull; with the Git integration, push your code or simply redeploy.

3. Update dependencies and republish

   Run npm install , then rebuild and deploy.

4. Schema upgrades are automatic

   RP creates and upgrades the tables on startup, so no manual SQL is needed.

# 1. Back up the database
npx wrangler d1 export re-play --remote --output backup.sql

# 2. Pull the latest code and update dependencies
git pull
npm install

# 3. Rebuild and publish
npm run cf:deploy

10FAQ

11Appendix

11.1 Project structure

RP-Re_Player
├── src/                        # source code
│   ├── layouts/                # page layouts
│   ├── lib/                    # business logic (pseudo-mounts, subtitles, lyrics, themes …)
│   ├── pages/                  # route pages
│   │   ├── api/                # API endpoints
│   │   │   ├── admin/          # admin API
│   │   │   └── public/         # public visitor API
│   │   ├── Local/              # visitor media library
│   │   └── tree/               # native player
│   ├── styles/                 # global and theme styles
│   └── types/                  # type definitions
├── public/                     # static assets (fonts, icons, posters)
├── scripts/                    # build and local-run scripts
├── astro.config.mjs            # Astro configuration
├── wrangler.toml               # Cloudflare configuration
├── package.json                # project dependencies
└── LICENSE                     # MIT license

11.2 Links