Now you can continue on the command line with oc new-app --template=ghost-template or you can deploy this through the web console
Configuring your Ghost Blog
If you don’t want to change any settings, all of the defaults are set up for you to just hit create and go. Using the defaults, this will create the following:
1 persistent volume for your MySQL database (1Gi)
1 persistent volume for your Ghost blog content (5Gi)
1 secret for the MySQL database credentials
A MySQL deployment
A Ghost build (using the ghost-cli)
A Ghost deployment
A Ghost route
If using a platform like Red Hat OpenShift Online, a default route will be created for you, e.g., https://ghost-ghost-example.b9ad.pro-us-east-1.openshiftapps.com/. Be sure that you update your deployment with this URL by running
<span> </span><span>oc set env dc ghost url=https://$(oc get route ghost -o custom-columns=HOST:.spec.host --no-headers)</span>
If you’re not using a default route, simply provide your custom URL in the “Application Hostname” template parameter, and this will be filled in for you.
That’s it! The OpenShift S2I build system has some amazing capabilities in taking nothing more than a Git repository and deploying a full application. This is simply one use case of that.
In this blog post I want to introduce a nice little trick to make canary deployments possible only with Kubernetes StatefulSets and Services. First, let me give a bit of background on why I went down ...
Today, we’re making the Azure Service Operator available on OperatorHub.io to enable users to connect OpenShift clusters to Azure services, including EventHub, Azure SQL, CosmosDB, Storage Accounts, ...