cloudfall 0.7.0rc2__tar.gz → 0.7.0rc3__tar.gz

{cloudfall-0.7.0rc2 → cloudfall-0.7.0rc3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: cloudfall
-Version: 0.7.0rc2
+Version: 0.7.0rc3
 Summary: The operator's record for self-hosted servers run by an AI agent: Ansible executes, Cloudfall gates, verifies and keeps the receipts
 Project-URL: Homepage, https://cloudfall.dev
 Project-URL: Repository, https://github.com/cloudfall-dev/cloudfall

cloudfall-0.7.0rc3/changelog.d/81-database-claims.md

@@ -0,0 +1,8 @@
+### Fixed
+
+- The Neon guide says each database belongs to an application Cloudfall
+  deploys on the same server, and no longer suggests an app on another host
+  can reach it; the brownfield design's operation example uses a target
+  scope the schema accepts (`host`); the site no longer offers a PostgreSQL
+  on its own, and its navigation and footer links are easier to tap on a
+  phone (#81)

{cloudfall-0.7.0rc2 → cloudfall-0.7.0rc3}/docs/brownfield-design.md

@@ -216,7 +216,7 @@ Every playbook or role the team already runs becomes an operation:
 id: deploy
 playbook: playbooks/deploy.yml
 risk: mutating
-targets: component
+targets: host
 inputs:
   version: string
 preconditions:

{cloudfall-0.7.0rc2 → cloudfall-0.7.0rc3}/docs/neon-migration-guide.md

@@ -60,13 +60,22 @@ simply absent:
   (a Hetzner Cloud VPS is the proven reference), or a fresh one plus an
   hour to get there
 - The Neon application's connection details and console access
+- The application that uses the database, declared in the same project
+  so Cloudfall deploys it on the server (see Step 1)
 - Python 3.14 and [`uv`](https://docs.astral.sh/uv/) on the machine you
   run Cloudfall from
 
 ## Step 1: declare the PostgreSQL service
 
-One `Service` resource, with the major version matching Neon's (the Neon
-console shows it under application settings):
+Each database belongs to an application Cloudfall deploys on the same
+server: `databases[].application` names a declared `Application`, and that
+application needs at least one component. Declare the application first
+([getting started](getting-started.md)). A database on its own, for an app
+that stays on another host, is not supported yet
+([#81](https://github.com/cloudfall-dev/cloudfall/issues/81)).
+
+Then one `Service` resource, with the major version matching Neon's (the
+Neon console shows it under application settings):
 
 ```yaml
 ---
@@ -186,10 +195,9 @@ database will produce.
 
 ## Step 5: cut over the application
 
-Point the application's `DATABASE_URL` at the migrated database. For a
-co-located app this is the local peer-authenticated socket URL (no
-password, no TLS, no pooler); for an app elsewhere, route it the same
-way as any other declared service. Deploy, watch health, and keep writes
+Point the application's `DATABASE_URL` at the migrated database. The app
+runs on the same server, so this is the local peer-authenticated socket URL
+(no password, no TLS, no pooler). Deploy, watch health, and keep writes
 frozen until the app is verified against the new database.
 
 ## Step 6: wind down Neon

{cloudfall-0.7.0rc2 → cloudfall-0.7.0rc3}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "cloudfall"
-version = "0.7.0rc2"
+version = "0.7.0rc3"
 description = "The operator's record for self-hosted servers run by an AI agent: Ansible executes, Cloudfall gates, verifies and keeps the receipts"
 readme = "README.md"
 license = "AGPL-3.0-or-later"