🦎
Lizardware CMS
Tutorial duration: 15 mins

Deploy Your Site

Follow these steps to get your Lizardware CMS instance running on Cloudflare's global edge network.

1

Fork the Repository

Start by creating your own private copy of the Lizardware codebase on GitHub. No coding or terminal commands required!

  1. Navigate to the Lizardware Repository.
  2. Click the Fork button in the top right.
  3. Ensure "Copy the main branch only" is checked.
  4. Click Create fork.
[SCREENSHOT: GitHub Fork Button & "Main Branch Only" Checkbox]
2

Connect to Cloudflare

Now we'll point your Cloudflare account to that new fork you just created. This is the "Import from Git" flow—the fastest way to go live.

☁️Step-by-Step Deployment
  1. Go to dash.cloudflare.com.
  2. Navigate to **Workers & Pages** → **Create Application** → **Pages**.
  3. Click **Connect to Git** and choose the Lizardware fork you created in Step 1.
  4. On the **Build Configuration** screen:
    • Framework Preset: **None** (or **Next.js** if auto-detected)
    • Build Command: npm run build
    • Build Output Directory: .open-next

Critical Action Required

Under **Environment Variables (Production)**, you MUST add your Cloudflare API Token.
Name: CLOUDFLARE_API_TOKEN
Value: (Your Custom Token with D1/KV/R2 Edit permissions)

[SCREENSHOT PLACEHOLDER]
Workers & Pages > Create > Import Git > Build Settings & Variables
📋
GitHub Account
Free

To store your source code and content history.

Sign UpLog In
Cloudflare Account
Free

To host your site and global database.

Sign UpLog In
1

Create your own copy of the Lizardware codebase.

  1. Go to the Lizardware Repository .
  2. Click the Fork button (top right corner) to create a copy in your account.
    GitHub Fork Button Location
2

We use GitHub Actions to automatically create your database and deploy your site. You just need to provide credentials so GitHub can talk to Cloudflare.

  1. Get your Cloudflare Info:

    • Account ID & Project Name: Found on the right side of the Cloudflare Dashboard under Workers & Pages > Overview.
    • API Token: Go to My Profile > API Tokens.
      Create a Custom Token with permissions: Account (Read), D1 (Edit), KV (Edit), R2 (Edit), Workers Scripts (Edit).
      [SCREENSHOT PLACEHOLDER: Cloudflare API Token Creation Screen]

  2. Add "Secrets" to GitHub (Hidden Credentials):

    1. Go to your forked repository on GitHub.
    2. Click Settings > Secrets and variables > Actions.
    3. Staying on the Secrets tab, click New repository secret.
    4. Name: CLOUDFLARE_API_TOKEN
    5. Value: Paste your long API Token string.
    6. Click Add secret.

  3. Add "Variables" to GitHub (Visible Metadata):

    1. Click the Variables tab (next to "Secrets").
    2. Click New repository variable.
    3. Add CLOUDFLARE_ACCOUNT_ID (e.g. 49f...).
    4. Add CF_PROJECT_NAME (e.g. lizardware-cms).
    GitHub Variables Configuration Screen

  4. Trigger Deployment:

    Go to the Actions tab in your repo. You might see a "Deploy" workflow waiting or running. If not, make a small change (like editing README.md) to trigger it.

Why separation? Secrets remain encrypted and hidden forever. Variables are visible text for configuration.

[SCREENSHOT PLACEHOLDER: Cloudflare Worker Settings showing completion]
3

Once your Cloudflare Page finishes its first build, your site is live! Deployment typically takes 2-4 minutes once triggered.

Smart Login: If you're already logged into Cloudflare, clicking the "Visit Site" button in your dashboard will take you straight to your new home.

  1. Find your Pages URL (e.g. project-name.pages.dev) in the Cloudflare Dashboard under Workers & Pages.
  2. Visit the URL in your browser.
  3. You'll be automatically redirected to /setup.
  4. Follow the Setup Wizard:
    • Step 1 will verify your API Token and resources.
    • Choose your Business Type (e.g., Marketing, Software Dev).
    • Click Complete to initialize the content.

✨ No manual database creation required! The wizard handles the heavy lifting.

❓

Encountering Issues?

If the build fails or you see error messages in Cloudflare, don't panic. Our troubleshooting guide covers all common alpha-test issues.

🔴 Common: Build Failures

Usually caused by missing CLOUDFLARE_API_TOKEN in your Cloudflare build variables.
Fix: Ensure the token has "Edit" permissions for D1, KV, and R2.

🟠 Common: 500 Error on /admin

The admin dashboard requires correct bindings to talk to D1/KV.
Fix: Run the Resource Step in the Setup Wizard again or check Cloudflare permissions.

Open Troubleshooting Guide