Web Components are the entry point for any application. Each Web Component consists of 1 or more "web instances". Each is an individual web process powered by your application code, run side-by-side to handle a share of the traffic load.
Auto-deploy to web servers using git 'pagoda push', or update via SFTP and deploy from the dashboard. Once your code is loaded, scale up or down anytime using a dashboard slider.
200 MB RAM Always Free
>200 MB Billed Hourly
1 -25+ Instances
200 MB - 1GB RAM each
Web instances within a single web component are distributed across multiple servers, adding hardware failover to your app. As instances are added to your web component, they are purposely deployed on separate physical servers.
Pagoda Box clones your code repo into a write-access container identical to your live app instances. With write access we are able to:
Your prepped source code is assembled in a read-only package and deployed to new instances. Updated instances are deployed in parallel to your current instances, with access to your live database and shared writable directories. They do not yet accept traffic. At this point we:
When new instances are verified operational, incoming connections are rerouted. Once connections drain, old instances are decommissioned. We also:
Simple UI in your App Dashboard makes adding instances and/or increasing RAM allotted to each instance extrememly easy. Sudden surges in traffic can be handled by dragging a slider. Once the surge is over, scale back to a normal level.
Ensure the latest code is pushed to your git repo, then either "pagoda deploy" from the Command Line Terminal, or click "Deploy Latest" in the App Dashboard. Both the Pagoda CLI and dashboard provide options to deploy from a git branch, the commit history, or "Rollback" to previous deploys.
Dashboard analytics provide both a general overview and specfic details for each site component. Click the web component to compare site traffic and response time with instance RAM and CPU usage, and to expose scaling controls.
Include a YAML Boxfile config in your source code to manage options like PHP extensions, version, and much more. When Pagoda Box deploys, rolls back or scales, your Boxfile is used to configure the PHP environment for all new web instances.
Pagoda Box allows you to manage application code through Git or SFTP (lovingly called Vintage Mode). If you aren’t a Git Ninja, Vintage Mode allows you to manage your code, yet still benefit from code versioning and emergency rollbacks.
Scale PHP instances horizontally (recommended) and vertically in the dashboard, using point-and-click controls to configure (based on analytic information) and save.