add uptimekit

[iRazvan2745]

What is this PR about?

New PR of Uptimekit

Checklist

Before submitting this PR, please make sure that:

• [ X] I have read the suggestions in the README.md file https://github.com/Dokploy/templates?tab=readme-ov-file#general-requirements-when-creating-a-template
• [X ] I have tested the template in my instance, so the maintainers don't spend time trying to figure out what's wrong.
• [ X] I have added tests that demonstrate that my correction works or that my new feature works.

Issues related (if applicable)

Close automatically the related issues using the keywords: closes #ISSUE_NUMBER

Screenshots or Videos

[github-actions]

built with Refined Cloudflare Pages Action

⚡ Cloudflare Pages Deployment

Name	Status	Preview	Last Commit
templates	✅ Ready (View Log)	Visit Preview	495f22c

[Siumauricio]

Automated template check 🤖

This PR's template was imported into a test Dokploy instance (using the docker-compose.yml + template.toml from the PR head) and deployed, and its configured domains were then checked over HTTP.

Result: ❌ some issues need attention

uptimekit

• Deploy: error (86s)
• Container states at failure time: status-page-1: created · dash-1: created · redis-1: running · db-1: restarting · clickhouse-1: running
• Issues:
  • the deployment finished with ERROR (see log below)
• Deploy log (tail):

Container compose-reboot-wireless-program-9r8dkh-db-1 Error dependency db failed to start
dependency failed to start: container compose-reboot-wireless-program-9r8dkh-db-1 is unhealthy
Error: ❌ Docker command failed
Error occurred ❌, check the logs for details.

The test service is removed automatically after verification. Happy to re-test once the PR is updated.

[Siumauricio]

Tested this template on a live Dokploy instance and fixed the deploy failure. Pushed the fix to this branch (495f22c).

Root cause: the db service uses postgres:18-alpine, and the Postgres 18 official image moved PGDATA from /var/lib/postgresql/data to /var/lib/postgresql. Mounting the volume at the old path made the entrypoint abort, so the container restarted forever and the service_healthy dependency failed with dependency db failed to start.

Changes:

• Mount db_data at /var/lib/postgresql (Postgres 18 layout)
• Removed host port mappings — Dokploy routes traffic through domains/Traefik, so published ports are unnecessary and can collide
• Replaced hardcoded postgres/clickhouse passwords with generated ${password:32} template variables wired through POSTGRES_PASSWORD / CLICKHOUSE_PASSWORD
• Cleaned up unused DASH_PORT/STATUS_PAGE_PORT env vars and a dangling empty [[config.mounts]] section in template.toml

Verified: deploy completes successfully; dash responds with HTTP 200 ("UptimeKit") on its domain and status-page serves "Status Page | UptimeKit" (404 at root is expected until a status page is created).

[iRazvan2745]

Oh, I thought I pushed a fix for the Postgres issue, so sorry. Also now there are 2 versions, one using timescaledb and one with clickhouse, shall I add both?