The deployment manager allows Super User administrators to provision new websites for implementation. The Deployment Manager application is used to facilitate this workflow.
Concepts
The deployment environment our websites live on is comprised of two “services”. You can think of a service as a “gateway” to a specific version of our application. The “blue” service gate opens to one set of codebase changes while the “green” service gate opens to another set. It is not important for you to understand these at a deep level, the only important thing to understand for implementation purposes is that the latest version of code (i.e. any new features or bug fixes being tested) will exist on the active canary service (usually “green”) while more stable code-releases will exist on the production service (usually “blue”.)
An example workflow may include a client who encounters a bug while on the production service. That bug is then fixed by a support engineer and pushed up to our canary service. We then can update the given website’s service to be the active canary service and QA the bug fix on their site. If all looks good, we can deploy the bug fix to the stable release (production service) and move the client back to production/stable.
Production Service: the latest stable release of our platform codebase lives here. If in doubt, provision clients to the production service. Once a site is provisioned they may be moved from the production or canary service at a whim. Keep in mind changing services a site is on will change the underlying codebase the site uses.
Canary Service: any new features or testing happens on this service. It is possible it is identical to the code on the production service, but it is also possible it may vary.
\uD83D\uDCD8 Website Set-up & Configuration
Now that an organization, connection, and related channel distribution feed is configured, it is time to create the physical WordPress website that will display the property data; as well as allow the related client(s) to modify CMS content, consume form submissions, and take bookings.
Navigate to https://cloud-manager.cloud2-stg.rezfusion.com/ and log in when prompted using your NGen staging (for training purposes) credentials. If you only have one set of credentials then these are both your production & staging credentials.
Create a new website using the UI and save. The website’s ID must be lowercase with no special characters(no spaces, or anything other than lowercase letters.) Once created, it will take a few moments to show up within the list. Once it shows up within the list, please allow for 5-10 minutes for the SSL certificate to be provisioned. Once the certificate finishes (you won’t see a “secure connection warning” when visiting the website), then it is time to begin implementing the configured channel and organization from the previous section.
Select OK if all looks correct:
If successful, you should be redirected to the /sites list:
It can take some time, but this triggers (internally) a WordPress site installation process among SSL certificate provisioning, etc.
NAME COMPLETIONS DURATION AGE implementation-install-415 0/1 91s 91s
There is no live indicator/notification (yet) for when the site is done. Simply refreshing the /sites page of the dashboard is sufficient to determine when it is complete. If it shows up, it is done (aside from potentially provisioning secure site certificates.)
A fresh site should be provisioned shortly (5-10 mins) after creation:
Log in to WordPress by visiting /wp-admin (i.e. https://bttessentials.rezfusion.com/wp-admin)
Enable the Formidable Plugins (if not, already):
The forms will auto-populate:
Enable the WPCode Lite Plugin:
Navigate to “Hub API Settings” and configure the channel ID and channel organization values:
Navigate to the search page and confirm the feed looks accurate:
Confirm checkout flow works & confirmation page works:
Confirm you can navigate to step 1 of checkout and the travel insurance, damage waiver, etc. look accurate:
Confirm you can reach secure SPS checkout:
