Skip to main content

Documentation Index

Fetch the complete documentation index at: https://www.sunny-dev.info/llms.txt

Use this file to discover all available pages before exploring further.

This guide explains how to configure a Web App as your next service in Revolte, covering both Repo Preference and Environment Settings. Visual references are provided for each step.
1

Choose a Preset

Choose Web App PresetThe preset chooser shows a grid of service options. The Webapp tile is highlighted, described as a standard service for frontend applications (React, Next.js, Vite, etc.). Click Web App to continue.
2

Repo Preference

The Repo Preference tab is identical across all service presets. See Repository Preference for a full walkthrough of each setting.
3

Web App — Environment Settings

Web App tab — QA environmentThe QA environment tab is selected. You can define independent resource properties for Preview, QA, Staging, and Production.The center panel shows the Web App form for the active environment:
  • Service Name — Enter a unique identifier for this service (e.g., frontend_app).
  • Entry Point — The main file that starts the service (e.g., index.js).
  • Properties
    • Index Page — The default page served for the root path (e.g., index.html).
    • Error Page — The page served for 404 or other errors (e.g., index.html for SPAs).
    • Enable CDN — Toggle to serve assets via Revolte’s global edge network for faster delivery.
4

Variables & Secrets

Configure environment variables and encrypted secrets for your web application. See Variables & Secrets for a detailed guide on managing environment-specific configurations.
5

Commit

At the bottom of the panel, fill in the Commit Details:
  • File Name — The configuration file to create or update in your repository (e.g., revolte.yml).
  • Commit Message — A short description of what you configured (e.g., Add web app).
  • Choose Branch — The branch where the configuration file will be committed.
Click Commit to save the configuration to your repository, or Skip & deploy to deploy immediately without committing.
Tip: For Single Page Applications (SPAs), set the Error Page to index.html to ensure your frontend router handles all paths correctly.