Configuring CI Pipeline
In Codesphere, the CI Pipeline is the central Infrastructure as Code (IaC) recipe that defines how a landscape is built and deployed.
Configuring a Landscape
A Landscape defines how your services are deployed and connected. You can add Compute Runtimes (Reactives, Managed Containers, Cloud Native Deployments) and Managed Services, configure their resources, networking, and environment. For a deeper technical overview, see Landscapes & Workspaces.
Using CI Profiles
What is a CI Profile?
Landscape Lifecycle
A Landscape is a deployment configuration of your application and its architecture, defined by the ci.yml file. It specifies what services to run, how they connect, and how resources are allocated. Each Landscape instance comes with an associated Workspace—your cockpit for interacting with that specific Landscape. This article walks you through the complete lifecycle of a Landscape, from initial creation to deletion.
Headless services
Headless services let you add HTTP and HTTPS routing rules to the Workspace Router without creating a separate reactive. They are useful when you need to forward traffic to services outside the current landscape, such as endpoints in a Virtual Kubernetes Cluster, Managed Services, Landscape Managed Services, or an external HTTP service.
Installing Dependencies
Basic Usage
Environment Variables
Hardcoding sensitive data—such as API keys, database passwords, or tokens—presents a security risk. To mitigate this, Environment Variables decouple the configuration from the codebase. Codesphere manages these variables via encrypted storage, injecting them into the application at runtime.
Secret Management
Secret management is currently a preview feature. You are seeing an early version of this functionality, which may change in future updates as we continue to improve the experience.