You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+13-10Lines changed: 13 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -265,12 +265,12 @@ To upgrade postgres_ai monitoring to a newer version:
265
265
### Step 1: Update the CLI
266
266
267
267
```bash
268
-
npm install -g postgresai@latest
268
+
npm install -g postgresai@0.15.0
269
269
```
270
270
271
271
Or if you're using npx:
272
272
```bash
273
-
npx postgresai@latest --version # verify the new version
273
+
npx postgresai@0.15.0 --version # verify the new version
274
274
```
275
275
276
276
### Step 2: Stop running services
@@ -281,16 +281,20 @@ postgresai mon stop
281
281
282
282
### Step 3: Pull new Docker images and restart
283
283
284
-
The simplest approach is to re-run local-install, which updates the image tag and pulls new images:
284
+
`mon update` migrates `.env` (adds any newly-required keys) and pulls images while preserving your user-managed `instances.yml`. It does **not** change `PGAI_TAG`, so set the new image tag yourself first — otherwise `mon update` just re-pulls and restarts the *old* version:
285
285
286
286
```bash
287
-
postgresai mon local-install -y
287
+
# In your monitoring directory (typically ~/.postgres_ai/), edit .env and set
288
+
# PGAI_TAG to the version you are upgrading to (it should match your new CLI
289
+
# version), e.g. for the 0.15 line: PGAI_TAG=0.15.0
290
+
postgresai mon update
291
+
postgresai mon start
288
292
```
289
293
290
294
This will:
291
-
-Update the `PGAI_TAG` in`.env`(located in your monitoring directory, typically `~/.postgres_ai/` or your current working directory) to match the new CLI version
292
-
- Pull the latest Docker images
293
-
- Start the services with the new images
295
+
-Add any newly required`.env`keys for the newer stack (existing values, your secrets, and `instances.yml` targets are preserved)
296
+
- Pull the Docker images for the `PGAI_TAG` you set
297
+
- Start the services on the new images
294
298
295
299
> **Note:** The `.env` file contains configuration for the monitoring stack, including `PGAI_TAG` (the Docker image version tag), `REPLICATOR_PASSWORD` (generated password for the demo standby replication user), `VM_AUTH_USERNAME`, `VM_AUTH_PASSWORD`, and optionally `GF_SECURITY_ADMIN_PASSWORD` (Grafana admin password) and `PGAI_REGISTRY` (custom Docker registry). `postgresai mon local-install` preserves existing `REPLICATOR_PASSWORD` and `VM_AUTH_*` values or generates new ones when they are missing; Docker Compose requires these values and does not use known default passwords.
296
300
@@ -301,9 +305,8 @@ This will:
301
305
If you prefer more control:
302
306
303
307
```bash
304
-
# Update the PGAI_TAG in .env to match your CLI version
305
-
postgresai --version # check your CLI version
306
-
# Edit .env and set PGAI_TAG to the version number
308
+
# Update the PGAI_TAG in .env to match your target stack version
309
+
# Edit .env and set PGAI_TAG=0.15.0
307
310
308
311
# Migrate .env to add any newly-required keys (e.g. VM_AUTH_* for 0.15+)
Copy file name to clipboardExpand all lines: cli/README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,9 +10,9 @@ Command-line interface for PostgresAI monitoring and database management.
10
10
npm install -g postgresai
11
11
```
12
12
13
-
Or install the latest beta release explicitly:
13
+
For reproducible installs, pin the 0.15 release explicitly:
14
14
```bash
15
-
npm install -g postgresai@beta
15
+
npm install -g postgresai@0.15.0
16
16
```
17
17
18
18
Note: in this repository, `cli/package.json` uses a placeholder version (`0.0.0-dev.0`). The real published version is set by the git tag in CI when publishing to npm.
0 commit comments