From 4c1b2f6dab7576f43c54844230cbe2ed4beb9dd6 Mon Sep 17 00:00:00 2001 From: "sg-doc-holiday[bot]" <219201796+sg-doc-holiday[bot]@users.noreply.github.com> Date: Thu, 15 Jan 2026 11:33:52 +0000 Subject: [PATCH 1/7] reporting-analytics: update analytics.mdx Add an explicit prerequisites section and clarify that OpenOps can run without Analytics, but the Analytics view requires Analytics to be deployed. This is based on server changes that allow running without analytics. --- reporting-analytics/analytics.mdx | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/reporting-analytics/analytics.mdx b/reporting-analytics/analytics.mdx index f7e1b16..d782dee 100644 --- a/reporting-analytics/analytics.mdx +++ b/reporting-analytics/analytics.mdx @@ -11,6 +11,13 @@ You can visualize data that you collect with [OpenOps tables](/reporting-analyti In addition to OpenOps tables, OpenOps Analytics can connect to and visualize your existing data sources, such as CSV files, Google Sheets, Postgres databases, and more. +## Prerequisites + +* OpenOps Analytics must be deployed and reachable by the OpenOps app. +* You need the admin password for the Analytics portal (configured with `OPS_ANALYTICS_ADMIN_PASSWORD`). + +If Analytics is not deployed for your environment, the OpenOps app can still run, but the **Analytics** view is not available. + ## Analytics admin portal To configure data visualizations, click **Analytics** on the main navigation bar in OpenOps. When the **Analytics** view opens, click **Admin Panel** to proceed to the Analytics admin portal that is separate from the main OpenOps application. From 6e2ed99b7428ab20a6be4ecb02c41ba3decdf1e5 Mon Sep 17 00:00:00 2001 From: "sg-doc-holiday[bot]" <219201796+sg-doc-holiday[bot]@users.noreply.github.com> Date: Thu, 15 Jan 2026 11:34:05 +0000 Subject: [PATCH 2/7] reporting-analytics: update analytics.mdx Replace curly apostrophe with straight apostrophe to comply with the style guide apostrophes rule. --- reporting-analytics/analytics.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/reporting-analytics/analytics.mdx b/reporting-analytics/analytics.mdx index d782dee..d212432 100644 --- a/reporting-analytics/analytics.mdx +++ b/reporting-analytics/analytics.mdx @@ -22,7 +22,7 @@ If Analytics is not deployed for your environment, the OpenOps app can still run To configure data visualizations, click **Analytics** on the main navigation bar in OpenOps. When the **Analytics** view opens, click **Admin Panel** to proceed to the Analytics admin portal that is separate from the main OpenOps application. -To sign in to the Analytics portal, use `admin` as the username and the password defined with the `OPS_ANALYTICS_ADMIN_PASSWORD` variable in the `.env` file in your OpenOps installation folder. (If you haven’t changed the password, the default is `please-change-this-password-1`.) +To sign in to the Analytics portal, use `admin` as the username and the password defined with the `OPS_ANALYTICS_ADMIN_PASSWORD` variable in the `.env` file in your OpenOps installation folder. (If you haven't changed the password, the default is `please-change-this-password-1`.) If you don't have access to the OpenOps installation folder: From 247837db572c3087d81adc48aabb7cfa9a781f31 Mon Sep 17 00:00:00 2001 From: "sg-doc-holiday[bot]" <219201796+sg-doc-holiday[bot]@users.noreply.github.com> Date: Thu, 15 Jan 2026 11:34:21 +0000 Subject: [PATCH 3/7] getting-started: update local.mdx Update local deployment guide download URL and archive name to 0.6.14 to match the requested release version. --- getting-started/deployment/local.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/getting-started/deployment/local.mdx b/getting-started/deployment/local.mdx index b26a583..e7ab832 100644 --- a/getting-started/deployment/local.mdx +++ b/getting-started/deployment/local.mdx @@ -29,8 +29,8 @@ If you can't use the autoinstall script, follow the manual installation steps fo 2. Open a new terminal window and run the following command to create a folder and download the OpenOps release files: ```shell mkdir -p openops && cd openops && \ - curl -OL https://github.com/openops-cloud/openops/releases/download/0.6.13/openops-dc-0.6.13.zip && \ - unzip openops-dc-0.6.13.zip && cp -n .env.defaults .env + curl -OL https://github.com/openops-cloud/openops/releases/download/0.6.14/openops-dc-0.6.14.zip && \ + unzip openops-dc-0.6.14.zip && cp -n .env.defaults .env ``` 3. 4. Pull the images and run `docker compose`: From 1b13eb80c7c60a6ab4e2978baa1b937e4101a251 Mon Sep 17 00:00:00 2001 From: "sg-doc-holiday[bot]" <219201796+sg-doc-holiday[bot]@users.noreply.github.com> Date: Thu, 15 Jan 2026 11:34:34 +0000 Subject: [PATCH 4/7] getting-started: update local.mdx Update Ubuntu manual install snippet to download and unzip the 0.6.14 docker-compose release archive, keeping guide aligned with the requested version. --- getting-started/deployment/local.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/getting-started/deployment/local.mdx b/getting-started/deployment/local.mdx index e7ab832..6504061 100644 --- a/getting-started/deployment/local.mdx +++ b/getting-started/deployment/local.mdx @@ -54,13 +54,13 @@ You can now access the application by navigating to http://localhost. # create and change directory mkdir -p openops && cd openops # download the release file - curl -OL https://github.com/openops-cloud/openops/releases/download/0.6.13/openops-dc-0.6.13.zip + curl -OL https://github.com/openops-cloud/openops/releases/download/0.6.14/openops-dc-0.6.14.zip # refresh package lists sudo apt update # install unzip sudo apt install unzip # decompress release file - unzip openops-dc-0.6.13.zip + unzip openops-dc-0.6.14.zip # copy the defaults to env without overwriting existing files cp --update=none .env.defaults .env ``` From 2c7ed601d2bc5dd1af240353e48bbe6f50fb22fa Mon Sep 17 00:00:00 2001 From: "sg-doc-holiday[bot]" <219201796+sg-doc-holiday[bot]@users.noreply.github.com> Date: Thu, 15 Jan 2026 11:34:48 +0000 Subject: [PATCH 5/7] getting-started: update local.mdx Update Windows manual install snippet to download and extract the 0.6.14 docker-compose release archive, consistent with the requested version. --- getting-started/deployment/local.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/getting-started/deployment/local.mdx b/getting-started/deployment/local.mdx index 6504061..9c62ac0 100644 --- a/getting-started/deployment/local.mdx +++ b/getting-started/deployment/local.mdx @@ -99,8 +99,8 @@ You can now access the application by navigating to http://localhost. ``` 3. Download the OpenOps release files: ```powershell - Invoke-WebRequest -Uri "https://github.com/openops-cloud/openops/releases/download/0.6.13/openops-dc-0.6.13.zip" - Expand-Archive -Path "openops-dc-0.6.13.zip" -DestinationPath . + Invoke-WebRequest -Uri "https://github.com/openops-cloud/openops/releases/download/0.6.14/openops-dc-0.6.14.zip" + Expand-Archive -Path "openops-dc-0.6.14.zip" -DestinationPath . if (-Not (Test-Path ".env")) { Copy-Item ".env.defaults" ".env" } From 355a05e1e84811ff767b2eaff371f0c1940dd811 Mon Sep 17 00:00:00 2001 From: "sg-doc-holiday[bot]" <219201796+sg-doc-holiday[bot]@users.noreply.github.com> Date: Thu, 15 Jan 2026 11:35:41 +0000 Subject: [PATCH 6/7] getting-started: update updating-openops.mdx Bump the manual update example command from 0.6.13 to 0.6.14 so the update guide matches the requested release version in this task. --- getting-started/updating-openops.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/getting-started/updating-openops.mdx b/getting-started/updating-openops.mdx index 01ff448..0da1147 100644 --- a/getting-started/updating-openops.mdx +++ b/getting-started/updating-openops.mdx @@ -28,8 +28,8 @@ The script will stop all running containers, pull the latest images, and restart ``` 4. Download and extract the new version: ```shell - curl -OL https://github.com/openops-cloud/openops/releases/download/0.6.13/openops-dc-0.6.13.zip && \ - unzip -o openops-dc-0.6.13.zip + curl -OL https://github.com/openops-cloud/openops/releases/download/0.6.14/openops-dc-0.6.14.zip && \ + unzip -o openops-dc-0.6.14.zip ``` (This code sample refers to a specific version. Don't forget to update it to the version you're installing.) 5. Fetch the new images and restart the application: From 84480d1c000f3eb127aec87fdb8c40284045c3f1 Mon Sep 17 00:00:00 2001 From: "sg-doc-holiday[bot]" <219201796+sg-doc-holiday[bot]@users.noreply.github.com> Date: Thu, 15 Jan 2026 11:37:03 +0000 Subject: [PATCH 7/7] reporting-analytics: update analytics.mdx Add a short, grounded section describing analytics seeding behavior and conditions (OPS_ANALYTICS_PRIVATE_URL and SHOW_DEMO_HOME_PAGE flag) based on server-side seeding code, while keeping existing user instructions intact and scannable. --- reporting-analytics/analytics.mdx | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/reporting-analytics/analytics.mdx b/reporting-analytics/analytics.mdx index d212432..7a9f66a 100644 --- a/reporting-analytics/analytics.mdx +++ b/reporting-analytics/analytics.mdx @@ -18,6 +18,13 @@ In addition to OpenOps tables, OpenOps Analytics can connect to and visualize yo If Analytics is not deployed for your environment, the OpenOps app can still run, but the **Analytics** view is not available. +## Analytics seeding behavior + +OpenOps runs an internal Analytics seeding step during startup. + +* If `OPS_ANALYTICS_PRIVATE_URL` is not configured, the seeding step is skipped. +* If the `SHOW_DEMO_HOME_PAGE` flag is not enabled, seeding the demo **Homepage** dashboard is skipped. + ## Analytics admin portal To configure data visualizations, click **Analytics** on the main navigation bar in OpenOps. When the **Analytics** view opens, click **Admin Panel** to proceed to the Analytics admin portal that is separate from the main OpenOps application.