Self-Hosted, Headless, and Hyper-Automated: The Backyard DevOps Stack for Backdrop Applications (Part 2)

In Part 1, we talked about using Backdrop CMS to run your entire business, from job tracking to stadium screens. Now, let’s get our hands dirty and talk infrastructure. If your business apps are critical, you need speed, reliability, and full control over your data.

We're trading expensive cloud bills and vendor lock-in for a lean, powerful, self-hosted infrastructure stack that keeps you in the driver's seat.

This is a deep dive into what DevOps need to develop, deploy, and automate your mission-critical Backdrop applications:

A dragon's eye view of finding content in Backdrop

Out of the box, Backdrop CMS has Views that can have exposed filters and Search.

However, there are modules that can extend the capability of Views and Search including integration with third party solutions including AI.  The purpose of this session is to give a high level overview of the options with very brief demos.  The idea being if there is demand to dig deeper, these sessions can be added later in the unconference.

Configuration Recipes

In short, config recipes are simple modules that add functionality to your site mostly by adding some prepared configuration. They do not add new features that are not already available through Backdrop Core or existing contrib modules. 

Available config recipes at this time:

Pages