Every time you or your customer/client launches a new site through your Dollie install, a sequence of events happens behind the scenes to ensure a perfectly deployed WordPress site. Your installation sends secured API requests to the Dollie Orchestration layer, which then starts the container deployment process. Below a simplified breakdown of this process.
- You go to the “Launch Site” page inside your Dollie installation and fill in mynewsite.yourdomain.com
- A secured API request is sent to the Dollie orchestration layer to deploy mynewsite.yourdomain.com under your partner account.
- The new Docker container is deployed to your Node and all services (PHP/NGINX/MySQL/Redis) are started inside the container. All of this happens in under 30 seconds.
- Once this process is complete the API request returns a result code (ie. Code 200, success!) and this triggers a redirect to the Site Setup Wizard.
- During the Site Setup you give your new site a name and create an admin account. These details are once again sent to your new WordPress container using the Dollie API so that your new WordPress site is fully configured and ready to go within a minute.
- Dollie has now saved the details of the newly deployed site in your database and your new site is listed under “Containers” in your WordPress admin. Now every time you visit the “Site Dashboard” of your deployed site, the Dollie API retrieves all of the details of the WordPress installation (plugin, themes, backups available, security status) to build out the dashboard that’s used by you and your customers to manage their site.
What runs inside these containers?
Inside every container a robust next-generation web stack is deployed to ensure a high-performance WordPress installation with self-healing capabilities. What this means is that every WordPress site is housed in its own isolated container, which has all of the software resources required to run WordPress optimally (Nginx, PHP, MySQL and when needed Redis/Memcached).
MySQL databases are hosted on a highly optimized dedicated node inside the same cluster which results in faster queries and quicker page load times.