Penguin is where you manage your WordPress pipelines. Penguin uses a continuous integration pipeline to provision, build and deploy WordPress resources into a cloud account of your choice.
- Turn key continuous integration pipeline saves you time and frustration
- T-shirt size infrastructure configuration choices
- Automatically provision, build and deploy resources into your own cloud account when your WordPress source code changes
- Set up as many environments as you need through unlimited stages
- Confidently deploy new versions of your WordPress sites when you include post-deployment tests in your pipeline configuration
- Portal Access
- API Access
- Only pay for what you use pricing
- Email based technical support
How it Works
Penguin pipelines deploy your WordPress code into a Kubernetes cluster managed by Xilution Giraffe. Therefore, before you can provision a Penguin pipeline, you will need to provision a Giraffe pipeline.
Once you have provisioned a Giraffe pipeline, you create a new pipeline configuration through the Penguin Portal. Next, you provision a pipeline based on this configuration into the Xilution platform through the Penguin Portal. Provisioning a pipeline into the Xilution platform invokes it for the first time. Pipeline invocation includes provisioning cloud resources into your cloud account and building/deploying/testing your WordPress site.
The following diagram describes a Penguin pipeline in detail.
The pipeline uses xilution-cms-penguin-ci to determine how it executes and which resources are provisioned into your cloud account. The pipeline also reads from a GitHub repository that you specified in the pipeline configuration. This GitHub repository contains the source code for your WordPress site. Refer to xilution-cms-penguin-example for example WordPress site source code that integrates with Penguin.
Changes to xilution-cms-penguin-ci or your WordPress site source code cause the pipeline to be invoked.
Costs & Pricing
You are responsible for fees incurred through the use of resources provisioned into your cloud account by Xilution via Penguin. These fees are paid directly to your cloud provider through your cloud provider account. In addition to these cloud provider fees, Xilution charges the following fees per provisioned pipeline. Xilution fees are charged to the credit card associated with the organization or sub-organization to which the pipeline is associated on the first day of each month for pipeline usage incurred during the prior month.
At the moment, we only support AWS. We plan to add more cloud providers in the future.
|Small AWS WordPress Site Pipeline||0.12 USD per Hour|
The Penguin Portal is an easy to use web based interface where you can create, update, delete, provision and deprovision WordPress pipelines.
Add acceptance and/or load tests to your source code and we'll run them for you after we deploy your site.
We collect key metrics on resources Penguin provisions into your cloud account. This helps us determine if you are using your provisioned resource in the most efficient way.
When the key metrics that we monitor fall outside normal operating ranges, we will work with you to determine the best course of action.
From time to time, cloud resource standards change. We can automatically update your provisioned resources to the latest standards.
Want to customize your interaction with Penguin? Check out the Penguin API.
When you configure a Penguin managed WordPress pipeline, you are eligible for technical support. To contact our technical support, send an email to firstname.lastname@example.org with a detailed description of your question or issue and we'll respond within one business day.
Email email@example.com with any questions you may have about Penguin or the Xilution platform in general.