feat(service): add InfluxDB template

[shtse8]

Changes

• Add InfluxDB 2.x as a new one-click service template
• InfluxDB is a high-performance time-series database with 1B+ Docker Hub pulls, widely used for metrics, events, and real-time analytics (popular with Grafana, Telegraf, Prometheus stacks)
• Template includes:
  • Official influxdb:2 Docker image
  • Automatic initial setup via environment variables (DOCKER_INFLUXDB_INIT_*)
  • Auto-generated admin username and password via Coolify SERVICE_USER / SERVICE_PASSWORD
  • Auto-generated admin token via SERVICE_PASSWORD_64_ADMINTOKEN
  • Configurable organisation and bucket name (with sensible defaults)
  • Persistent data and config volumes
  • Health check using the native influx ping command
  • InfluxDB SVG logo (from simple-icons)

Issues

• fixes:

Category

• Adding new one click service

Screenshots or Video (if applicable)

N/A — new template, no UI changes.

AI Usage

• AI is used in the process of creating this PR

Steps to Test

• Step 1 – Deploy Coolify and navigate to New Service
• Step 2 – Search for "InfluxDB" in the service list and select it
• Step 3 – Click Deploy and wait for the service to become healthy
• Step 4 – Open the assigned domain; you should be redirected to the InfluxDB UI and can log in with the generated username/password
• Step 5 – Verify the admin token is available as an environment variable (DOCKER_INFLUXDB_INIT_ADMIN_TOKEN) for use by downstream services (e.g. Telegraf, Grafana)

Contributor Agreement

Important

• I have read and understood the contributor guidelines. If I have failed to follow any guideline, I understand that this PR may be closed without review.
• I have tested the changes thoroughly and am confident that they will work as expected without issues when the maintainer tests them

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
26963785	Triggered	Company Email Password	548dc51	.claude/skills/pest-testing/SKILL.md	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[ShadowArcanist]

Untested PR