Developing applications on OpenShift in an easier way

Developing applications on OpenShift in an easier way

Have you ever developed applications on a platform like Red Hat OpenShift? I’m a Java developer with more than 15 years of coding experience, and while I’ve been working with OpenShift for over three years now, I never found it easy to use or compelling as a day to day development platform. Why? There are […]

Read More...

Promoting container images between registries with skopeo

OpenShift admins choose different architectures for their installations, but many use two discrete clusters to physically divide development and testing workloads from production deployments. We recommend having some Continuous Integration (CI) process in nearly every development scenario, to orchestrate the lifecycle of applications from the initial commit all the way into production. Continuous Integration can […]

Read More...

Care and Feeding of Minishift Development Environments

Care and Feeding of minishift Development Environments If you’ve heard of minishift, the OpenShift environment for your laptop, or if you’re using the Container Development Kit (CDK) at work, you’re probably building applications on the OpenShift Container Platform. This post is for you. If you’re new to OpenShift and these names aren’t familiar yet, check […]

Read More...

Enhancing your Builds on OpenShift: Chaining Builds

Enhancing your Builds on OpenShift: Chaining Builds

In addition to the typical scenario of using source code as the input to a build, OpenShift build capabilities provides another build input type called “Image source”, that will stream content from one image (source) into another (destination).

Using this, we can combine source from one or multiple source images. And we can pass one or multiple files and/or folders from a source image to a destination image. Once the destination image has been built it will be pushed into the registry (or an external registry), and will be ready to be deployed.

Read More...