Shared settings concepts
Most apps can store environment variables through app settings. Current environment-variable validation:- keys must be uppercase shell-style identifiers
- each value has a maximum length
- the total count is capped
Settings by app type
React
Servbase controls key build settings for safety:- build command is restricted to supported values
- publish directory defaults to
dist - package manager is normalized
Python
Customer-editable settings currently focus on:- environment variables
- runtime log enablement
- Gunicorn worker count
- optional Gunicorn worker class
- start command
- root directory
- publish directory
Node.js / Express.js
Current managed settings behavior includes:- framework-aware runtime handling for Node-style apps
- platform-managed runtime behavior with a start command path
- environment-variable support
Next.js
Current Next.js settings behavior includes:nextjs_modeselectionssr,csr, andssgrendering modes- SSR using a runtime path
- CSR and SSG using static build output behavior
PHP
PHP apps accept environment variables but do not expose a customer build pipeline in the same way as React.Runtime logs
runtime_app_logs_enabled controls whether the Python runtime log endpoints are available.
Gunicorn options
Current Python Gunicorn settings are accepted only for supported frameworks:- Flask
- Django
If the user sends a value above the plan limit, the API rejects it with a plan-aware validation error.
Source-sensitive settings
For GitHub-sourced apps, branch updates remain part of the configuration surface. When rebuild is available for the app and the app is connected to GitHub, the customer-facing rebuild choice is between:githubworkspace