Deploying your project on the Civic Cloud

This is the path for a project team bringing an app onto a CodeForPhilly cluster, or adding something to an app that’s already here. It assumes you know your own app and Docker, and nothing about this repo.

There are two clusters, each with its own repo: sandbox (cfp-sandbox-cluster, *.sandbox.k8s.phl.io) and live (cfp-live-cluster, *.live.k8s.phl.io and real domains). They have the same layout. Everything lands on sandbox first.

Read in order the first time; each page is short.

1. How deploys work: nothing is applied by hand. You change files, a pipeline turns them into manifests, and a second pull request shows you exactly what will change before it does.
2. Your project in the repo: the handful of files that make up a project here, which ones you own, and the one rule about where raw manifests can go.
3. Shared PostgreSQL: what the shared database cluster gives you, then three pages in order:
   • Provision a database: a user and an empty database, in four files, none of them shared infrastructure.
   • Connect your app: reading the connection settings and password, for helm and for kustomize apps, and the order to land things in.
   • Data and backups: getting a psql shell, loading existing data, and what the backups do and don’t give you.
4. Reference: the directory map and the gotchas, for when you already know the shape.

The running example is a made-up example-app that is moving from a Postgres container inside its own pod to the shared cluster. Substitute your app’s name wherever you see it.

If you get stuck, ask in #civic-cloud on the Code for Philly Slack.