Skip to content

v1.4.0: add uptime kuma and pgvector support#53

Merged
kossakovsky merged 7 commits into
mainfrom
develop
Mar 16, 2026
Merged

v1.4.0: add uptime kuma and pgvector support#53
kossakovsky merged 7 commits into
mainfrom
develop

Conversation

@kossakovsky

@kossakovsky kossakovsky commented Mar 16, 2026

Copy link
Copy Markdown
Owner

Summary

  • Uptime Kuma — self-hosted uptime monitoring with 90+ notification services
  • pgvector — switch PostgreSQL image to pgvector/pgvector for vector similarity search support
  • Fix missing README service URL and update preview tracking for Uptime Kuma

Changelog

See CHANGELOG.md for full details under [1.4.0] - 2026-03-15.

Test plan

  • docker compose -p localai config --quiet passes
  • bash -n scripts/update_preview.sh passes
  • PostgreSQL container starts with pgvector/pgvector:pg17 image
  • Existing PostgreSQL data volume mounts without issues
  • CREATE EXTENSION vector; works inside postgres container
  • Uptime Kuma accessible via Caddy reverse proxy
  • Welcome page shows Uptime Kuma service card

Summary by CodeRabbit

  • New Features

    • Added Uptime Kuma for self-hosted uptime monitoring with 90+ notification services.
    • PostgreSQL now includes pgvector for vector similarity search capabilities.
  • Documentation

    • Updated README and CHANGELOG with new service information.

kossakovsky and others added 7 commits March 12, 2026 20:30
fix healthcheck port (3000→3001), add missing logging config,
add UPTIME_KUMA_HOSTNAME to caddy env, add import service_tls
in caddyfile, fix hostname typo in .env.example, add uptime-kuma
to GOST_NO_PROXY, fix profile name in wizard/final report, fix
env var in welcome page generator, add missing trailing comma in
app.js, move changelog to Added section, declare volume in
top-level section, fix container name in caddyfile, fix volume
mount path, fix broken markdown link in README
feat: add Uptime Kuma uptime monitoring service
add missing readme service url, update preview image tracking,
and release changelog as v1.4.0
switch postgres image to pgvector/pgvector for vector
similarity search capabilities
@coderabbitai

coderabbitai Bot commented Mar 16, 2026

Copy link
Copy Markdown
📝 Walkthrough

Walkthrough

This PR integrates Uptime Kuma uptime monitoring service into the deployment infrastructure, adding configuration files, docker-compose definitions, wizard prompts, and welcome page metadata. PostgreSQL image is simultaneously upgraded to pgvector for vector similarity search support.

Changes

Cohort / File(s) Summary
Configuration & Environment
.env.example, Caddyfile
Added UPTIME_KUMA_HOSTNAME environment variable and GOST_NO_PROXY configuration. New Caddyfile site block for Uptime Kuma proxying to uptime-kuma:3001.
Documentation
CHANGELOG.md, README.md
Documented Uptime Kuma addition (90+ notification services) and pgvector PostgreSQL upgrade in 1.4.0 release notes. Added Uptime Kuma to installation tools list with access URL.
Docker Composition
docker-compose.yml
Added uptime-kuma service (louislam/uptime-kuma:2) with volume, healthcheck, and environment variables. Introduced uptime_kuma_data volume. Upgraded postgres image from postgres to pgvector/pgvector variant. Added UPTIME_KUMA_HOSTNAME to caddy service environment.
Installation Scripts
scripts/04_wizard.sh, scripts/07_final_report.sh, scripts/generate_welcome_page.sh, scripts/update_preview.sh
Added uptime-kuma service entry to wizard offerings. Added conditional credential reporting in final report when profile is active. Integrated Uptime Kuma JSON entry into welcome page data with hostname and account creation note. Updated postgres image tag and added uptime-kuma image update checks for preview mode.
Frontend Service Metadata
welcome/app.js
Added uptime-kuma entry to SERVICE_METADATA with name, description, monitoring category, custom icon/color, and documentation link.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

Poem

🐰 A new Uptime friend arrives today,
Watching services 'round the clock to stay,
With pgvector's vector sight,
Our databases shine so bright!
Hop-hop, the infrastructure's here to play! 🎉

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately summarizes the two main additions in the changeset: Uptime Kuma integration and pgvector support for PostgreSQL.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
  • 📝 Generate docstrings (stacked PR)
  • 📝 Generate docstrings (commit on current branch)
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch develop
📝 Coding Plan
  • Generate coding plan for human review comments

Comment @coderabbitai help to get the list of available commands and usage tips.

@kossakovsky kossakovsky self-assigned this Mar 16, 2026

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
docker-compose.yml (1)

547-553: ⚠️ Potential issue | 🟡 Minor

Align Postgres healthcheck timings with repository standard.

In this service, Lines 551-553 currently use 3s/3s/10, which deviates from the project Compose healthcheck baseline.

Suggested patch
   postgres:
     container_name: postgres
     image: pgvector/pgvector:pg${POSTGRES_VERSION:-17}
     restart: unless-stopped
     healthcheck:
       test: ["CMD-SHELL", "pg_isready -U postgres"]
-      interval: 3s
-      timeout: 3s
-      retries: 10
+      interval: 30s
+      timeout: 10s
+      retries: 5
As per coding guidelines: `Define healthchecks for services with proper timeout and retry configuration (interval: 30s, timeout: 10s, retries: 5)`.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@docker-compose.yml` around lines 547 - 553, The Postgres service healthcheck
currently uses non-standard timings (test: "pg_isready -U postgres" with
interval: 3s, timeout: 3s, retries: 10); update the healthcheck block for that
service to match repository baseline by setting interval: 30s, timeout: 10s,
retries: 5 while keeping the existing test command (pg_isready -U postgres) and
image declaration (pgvector/pgvector:pg${POSTGRES_VERSION:-17}) unchanged.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Outside diff comments:
In `@docker-compose.yml`:
- Around line 547-553: The Postgres service healthcheck currently uses
non-standard timings (test: "pg_isready -U postgres" with interval: 3s, timeout:
3s, retries: 10); update the healthcheck block for that service to match
repository baseline by setting interval: 30s, timeout: 10s, retries: 5 while
keeping the existing test command (pg_isready -U postgres) and image declaration
(pgvector/pgvector:pg${POSTGRES_VERSION:-17}) unchanged.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 7d6a89a7-221f-4b98-b611-cadb2599c9d3

📥 Commits

Reviewing files that changed from the base of the PR and between 174fce7 and 463258f.

📒 Files selected for processing (10)
  • .env.example
  • CHANGELOG.md
  • Caddyfile
  • README.md
  • docker-compose.yml
  • scripts/04_wizard.sh
  • scripts/07_final_report.sh
  • scripts/generate_welcome_page.sh
  • scripts/update_preview.sh
  • welcome/app.js

@kossakovsky kossakovsky merged commit d344291 into main Mar 16, 2026
3 checks passed
@kossakovsky kossakovsky deleted the develop branch March 16, 2026 02:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant