Added Template GoClaw

[moskoweb]

Multi-agent AI gateway with teams, delegation & orchestration. Single Go binary, 11+ LLM providers, 5 channels.

[netlify]

❌ Deploy Preview for easypanel-templates failed.

Name	Link
🔨 Latest commit	4c1e77c
🔍 Latest deploy log	https://app.netlify.com/projects/easypanel-templates/deploys/69e1628e7ed7040008668c4d

[Ahson-Shaikh]

Thanks for the GoClaw template contribution — it’s a strong start and the overall structure is good.
Before we move this to production, a few changes are required to make it reliable and consistent with our template standards.

Required changes before merge

Fix schema consistency for providerApiKey
Right now providerApiKey is marked as required, but the same field is described as optional with an empty default.
Please make this consistent. If optional is intended, remove it from required.

Pin container images to immutable versions
The template currently uses mutable tags (:full, :latest).
For production templates, please pin exact versions (or digests) for both GoClaw app and GoClaw UI images.
Align runtime layout with upstream behavior (or document the divergence clearly)
Current env/mount path layout differs from upstream compose defaults (data/skills/workspace/session structure).
Please either align with upstream defaults, or explicitly document why this change is necessary and confirm it has been validated end-to-end.

Correct metadata link labeling
The Website link currently points to the GitHub repository.
Please either provide a real website URL or relabel/remove it to avoid duplicate GitHub references.

Recommended improvements (non-blocking but strongly suggested)

Add X-Forwarded-Proto and X-Forwarded-Host headers in nginx proxy config.
Double-check Postgres defaults (user/db naming and DSN assumptions) for future compatibility.
Validate and share smoke-test results for: fresh install, UI access, websocket route, provider key wiring, and restart persistence.

Once the required items are updated, I can re-review quickly for production readiness.

[Ahson-Shaikh]

For serviceName and other related serviceNames, we prefer serviceName: input.appServiceName and input.appServiceName-db and so on for any other service.

[moskoweb]

I made the suggested adjustments.

[Ahson-Shaikh]

Have you also tested the PR on Easypanel?

[Ahson-Shaikh]

Why did you need to specify this? The managed postgres instance would have its mounts already defined

[moskoweb]

It was necessary because PGVector 18 changed the file folder, and Easypanel didn't from version 16 to 18, and without that, it gave an error about the data loading folder.