Deploying Your Site

Pala provides a streamlined deployment process powered by Cloudflare's global edge network. This guide explains how deployments work and how to manage your site's publishing workflow.

How Deployments Work

Architecture Overview

Pala uses Cloudflare's infrastructure to serve your sites:

• A Cloudflare Worker handles request routing and serving content

• Site files are stored in Cloudflare R2 buckets

• Content is served from Cloudflare's global edge network for optimal performance

Staging and Live Environments

Your site maintains two environments:

• Staging: Where generated sites are uploaded to before publishing

• Live: The production environment that visitors see

Publishing Workflow

Making Changes

When you edit content or modify your site:

1. Changes are automatically saved

2. The affected pages are regenerated as static HTML

3. Updated files are uploaded to the /staging folder in your site's R2 bucket

Publishing Changes

To make your changes live:

1. Click the "Publish" button in the Pala interface

2. The contents of the /staging folder are copied to /live

3. Your changes are instantly available to visitors

Accessing Your Site

Default Domain

Every site is automatically assigned a subdomain for immediate access:

• On Pala Cloud: your-site-id.palacms.site

• For self-hosted installations: Configure your preferred subdomain through Cloudflare

Technical Details

For developers who need to understand the deployment architecture:

Site Structure
└── R2 Bucket
    ├── /staging
    │   └── [Generated HTML files]
    └── /live
        └── [Production HTML files]

The Cloudflare Worker:

• Routes requests to the appropriate environment

• Serves files from the R2 bucket

• Handles caching and edge distribution

All deployments are atomic, ensuring zero-downtime updates when publishing changes.