mirror of
https://github.com/hanzo-apps/templates.git
synced 2026-10-30 14:48:30 +00:00
zeekay
cf4d0b027e
Aggregates five OSS one-click/self-hosting catalogs into the Dokploy blueprint
shape the Hanzo PaaS consumes (meta.json array + blueprints/<id>/{template.toml,
docker-compose.yml,meta.json,logo}):
Dokploy 500 (MIT, verbatim) · Coolify 174 (Apache-2.0) · CapRover 161
(Apache-2.0) · CasaOS 85 (Apache-2.0) · Runtipi 110 (GPL-3.0)
Deduped by app identity; each source + app keeps its upstream license
(ATTRIBUTION.md). Deterministic aggregators + a hard validator (every
template.toml parses with the platform's toml lib, every compose parses as YAML,
meta.json is the expected array, and an over-HTTP fetch probe exercises all
1030) — 0 hard failures. Served natively by hanzoai/static on DOKS (no CDN/Pages/
Vercel); CI builds on the hanzo-build-linux-amd64 arc pool; operator App CR in
crs/ serves it at templates.hanzo.ai.
2.0 KiB
2.0 KiB
Trigger.dev Setup Instructions
Deploy
- In Dokploy, create the service from the Trigger.dev template.
- Dokploy generates all required secrets (
MAGIC_LINK_SECRET,SESSION_SECRET,ENCRYPTION_KEY, database credentials, etc.) automatically. - Deploy and wait until the containers are running. The main domain points to the
webappservice (port3000).
If you serve the app over HTTPS, set TRIGGER_PROTOCOL=https in the Environment tab (the template defaults to http) so that login links use the correct scheme, then redeploy.
First login (no email server configured)
Trigger.dev logs you in with magic links sent by email. The template does not configure an email transport by default, so the email is never actually sent. Instead, the magic link is printed to the logs of the webapp container:
- Open
https://<your-domain>and enter your email address to request a magic link. - In Dokploy, go to your Trigger.dev service, open the Logs tab, and select the
webappcontainer/service. - Look for a recent log entry containing a URL like
.../magic?token=...(search formagic). - Copy that URL into your browser to complete the login.
Configure email sending (optional)
To have magic links delivered by email, add these variables in the Environment tab and redeploy.
Using SMTP:
EMAIL_TRANSPORT=smtp
[email protected]
[email protected]
SMTP_HOST=smtp.example.com
SMTP_PORT=587
SMTP_SECURE=false
SMTP_USER=your-smtp-user
SMTP_PASSWORD=your-smtp-password
Using Resend:
EMAIL_TRANSPORT=resend
[email protected]
[email protected]
RESEND_API_KEY=your-resend-api-key
Restrict who can sign up (recommended)
By default anyone who can reach the webapp can request a magic link. Restrict access with a regex of allowed email addresses:
WHITELISTED_EMAILS=you@example\.com|teammate@example\.com
You can also grant admin rights by email with ADMIN_EMAILS (same regex format).