Deploy UI - Web Interface for Builds and Deployments

A web interface for starting builds and deployments from the browser.

URL

http://localhost:4000/auth/deploy.html

Features

1. Project Configuration

Field	Description	Required	Default
Project Name	Project name (slug format)	Yes	-
Target Platform	www / ios / android	Yes	www

Build branch, license, and GraphQL schema min version are set automatically (branch from build-info, license always FREE, gqlSchemaMinVersion = 1).

2. Recipe JSON

Textarea for recipe JSON configuration:

{
  "components": {
    "header": {
      "type": "header",
      "config": {
        "title": "My App",
        "logo": "/logo.png"
      }
    },
    "footer": {
      "type": "footer",
      "config": {
        "copyright": "Copyright 2025"
      }
    }
  }
}

Validation:

JSON is validated on submit
Parse errors are shown in the UI

3. GitHub Authorization (Optional)

Three modes are available:

Mode 1: No GitHub Deploy

Build only, no GitHub publish
Result is saved as a tar archive

Mode 2: Use Existing JWT Token

Paste a previously generated JWT
Token can be created via /auth/generate-jwt
Useful for repeated deployments

Example:

eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJ0eXBlIjoiZGVwbG95Ii...

Mode 3: Authorize with GitHub

Opens OAuth authorization in a popup
Automatically selects repo and generates JWT
JWT is inserted into the form
Popup closes after success

Flow:

Click "Authorize with GitHub OAuth"
Popup opens /auth/github/start
Complete GitHub authorization
Select repository on /auth/success.html
JWT is sent to the form via window.postMessage
Popup closes automatically

Submit the Form

When you click "Start Build & Deploy":

Validation
- Recipe JSON is parsed
- Required fields are checked

Request creation

POST /process
Content-Type: application/json

{
  "projectName": "my-app",
  "target": "www",
  "recipe": { ... },
  "githubJwt": "..." // optional
}

branch (current build branch), license: "FREE", and gqlSchemaMinVersion: 1 are inserted automatically.

Result display
- JSON response is shown
- Status badge: queued / in-progress / canceling / canceled / done / error
- Success or error messages are shown

Queue and Cancellation

If all slots are busy, builds are queued (queued status).
Queue position is shown for waiting builds.
The UI has a Cancel Build button for queued or running builds.
Cancellation is also available via API:
```
POST /build-status/:dataHash/cancel
```
Status changes to canceling, then canceled.

Usage Examples

Example 1: Build without GitHub

Set Project Name: my-awesome-app
Select Target: www
Paste recipe JSON
Keep "No GitHub Deploy"
Click "Start Build & Deploy"

Result: Tar archive download URL in the response

Example 2: Build with Existing JWT

Fill project configuration
Paste recipe JSON
Select "Use Existing JWT Token"
Paste JWT token into textarea
Click "Start Build & Deploy"

Result: Build and publish to GitHub repository

Example 3: Build with OAuth

Fill project configuration
Paste recipe JSON
Select "Authorize with GitHub"
Click "Authorize with GitHub OAuth"
In the popup:
- Complete OAuth authorization
- Select owner and repository
- Adjust path if needed
- Click "Generate JWT Token"
JWT is inserted into the form
Click "Start Build & Deploy"

Result: Build and publish to the selected GitHub repository

Technical Details

postMessage Integration

OAuth popup sends a message to the parent window:

window.opener.postMessage({
  type: 'github-jwt',
  jwt: 'eyJhbGci...'
}, window.location.origin);

Deploy form listens for messages:

window.addEventListener('message', (event) => {
  if (event.data.type === 'github-jwt') {
    document.getElementById('githubJwt').value = event.data.jwt;
    // Switch to JWT mode
    authJwt.checked = true;
    // Close popup automatically
    oauthWindow.close();
  }
});

Response Format

Successful build:

{
  "status": "done",
  "dataHash": "abc123...",
  "url": "abc123.42.pub",
  "publish": {
    "archive": {
      "status": "done",
      "url": "/dist/abc123/build.tar"
    },
    "github": {
      "status": "done",
      "repo": "owner/repo",
      "branch": "main",
      "commit": "def456..."
    }
  }
}

Error:

HTTP 400: Invalid recipe JSON

Security

JWT tokens are not logged
postMessage checks origin
Recipe is validated on the server
Sensitive data is not stored in localStorage

URL Parameters

?example

Loads a sample recipe:

http://localhost:4000/auth/deploy.html?example

Integration with Other Pages

Home Page (/) - "Deploy Now" button
Success Page (/auth/success.html) - sends JWT via postMessage
GitHub OAuth (/auth/github/start) - authorization for JWT generation