What if you could deploy to the cloud without writing a Dockerfile? Learn how buildpacks automate containerization for a simpler, faster CI/CD pipeline.
#1about 5 minutes
Understanding the core philosophy of Cloud Foundry
Cloud Foundry abstracts infrastructure complexity, allowing developers to deploy source code directly to the cloud without managing underlying configurations.
#2about 6 minutes
A high-level overview of Cloud Foundry architecture
Key components like the Go Router for routing, UAA for authentication, and Diego for container lifecycle management work together to run applications.
#3about 7 minutes
Organizing work with organizations and spaces
Cloud Foundry uses a two-level hierarchy of organizations and spaces to manage access, resources, and application environments for different teams or projects.
#4about 3 minutes
Automating deployment with service accounts
Service accounts provide scoped, non-personal credentials that can be created through the marketplace for use in automated CI/CD pipelines.
#5about 16 minutes
Building a deployment pipeline with GitHub Actions
A GitHub Actions workflow automates the process of building a Java application, authenticating with the CF CLI, and pushing the artifact to Cloud Foundry.
#6about 8 minutes
How buildpacks automatically containerize your application
Buildpacks are scripts that detect the application type, compile dependencies, and package the code into a runnable container image called a droplet, automating containerization.
#7about 5 minutes
Verifying the deployment and application logs
After a successful pipeline run, the deployed application appears in the Stratos UI, where its status, logs, and public route can be inspected.
#8about 4 minutes
How application scaling works in Cloud Foundry
Applications are scaled horizontally by adjusting the number of instances, either manually via the CLI or automatically using an autoscaler based on metrics like CPU load.
#9about 2 minutes
Understanding container security on Cloud Foundry
Security is managed through secure community buildpacks, network traffic rules via Application Security Groups (ASGs), and integrating scanning tools into the pipeline.
#10about 7 minutes
Migrating applications and the stateless requirement
Cloud Foundry is best suited for stateless, 12-factor applications, as it does not provide persistent storage, requiring state to be managed in external data services.
#11about 6 minutes
Differentiating between container, cloud, and serverless
A high-level explanation clarifies that containers package applications, cloud provides virtualized resources, and serverless executes functions on-demand.
Related jobs
Jobs that call for the skills explored in this talk.
Now is the time for industrialized software developmentNow is the time for industrialized software development
Recently, I received a letter from my car’s manufacturer alerting me to a recall. They had discovered a defective part and wanted to replace it.
It was easily fixed, and I might have forgotten a...
Christina Schaireiter
Why Attend a Developer Event?Modern software engineering moves too fast for documentation alone. Attending a world-class event is about shifting from tactical execution to strategic leadership.
Skill Diversification: Break out of your specific tech stack to see how the industry...
Dev Digest 216: CyberSec + Mythos, Stack Overflow for Agents & DOOM in TTFInside last week’s Dev Digest 216 .
🧠 Prompts are now tools in Chrome
📜 The AI Coding Agent Manifesto
🔐 How Claude Mythos changes Cyber Security
🧱 GitHub Stacked PRs to battle AI slop
⚙️ Git commands to run before reading code
🐍 A Python framework f...
From learning to earning
Jobs that call for the skills explored in this talk.