Repository navigation
[Script request]: Temps (temps.sh) #17484
Unanswered
shrijayan
asked this question in
Request script
Replies: 1 comment 1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Application Name
Temps
Official Website
https://temps.sh/
Source Repository
https://github.com/gotempsh/temps
Repository Stars
786
Minimum Adoption Requirement
Description
Temps is an open-source, self-hosted deployment platform in a single Rust binary. It replaces Vercel, Sentry, PostHog, Pingdom, Resend and E2B: git-push deployments with preview URLs, web analytics with funnels and session replay, error tracking, OpenTelemetry traces/metrics/logs, uptime monitoring, transactional email, and Firecracker/Docker AI sandboxes — all self-hosted, no per-seat pricing.
Why should this be added?
Homelab users who deploy their own apps currently stitch together Coolify plus separate analytics, error tracking, and monitoring services. Temps does this from one binary, so a single LXC replaces an entire stack of paid SaaS. It also imports existing setups from Coolify, Dokploy, CapRover, Portainer, Kamal, Kubernetes and plain Docker, which makes it a natural onboarding path for people already running containers on Proxmox.
Installation Notes
Official install is
curl -fsSL https://temps.sh/deploy.sh | bash, which installs Docker, TimescaleDB, SSL and the Temps binary. Tested upstream on Ubuntu 22.04/24.04 — a Debian 12 LXC would need verification. Suggested defaults: Debian 12 LXC, Docker + TimescaleDB, port 443/80 for the web UI, storage sized for app deployments. Note this installs Docker inside the container, so nesting must be enabled in the LXC config.Due Diligence
cc @dviejokfs — author/maintainer of Temps, in case they want to weigh in on the LXC install details above.
All reactions