deploy-to-temps

Featured

Deploy applications to the Temps platform with automatic framework detection, Dockerfile generation, and container orchestration. Supports Next.js, Vite, React, Node.js, Python, Go, Rust, Java, and C# applications. Use when the user wants to: (1) Deploy their app to Temps, (2) Set up CI/CD with Temps, (3) Configure deployment settings, (4) Create a Dockerfile for Temps, (5) Deploy a containerized application, (6) Set up automatic deployments from Git. Triggers: "deploy to temps", "temps deployment", "push to temps", "containerize for temps", "temps ci/cd".

DevOps & Infrastructure 655 stars 46 forks Updated today Apache-2.0

Install

View on GitHub

Quality Score: 92/100

Stars 20%
94
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Deploy to Temps Deploy applications to Temps with automatic framework detection and optimized builds. ## Supported Frameworks | Framework | Detection | Build Command | |-----------|-----------|---------------| | Next.js | `next.config.*` | `next build` | | Vite | `vite.config.*` | `vite build` | | Create React App | `react-scripts` in package.json | `react-scripts build` | | Remix | `remix.config.*` | `remix build` | | Express/Node.js | `express` in dependencies | `npm run build` (if exists) | | NestJS | `@nestjs/core` in dependencies | `nest build` | | Python/Flask | `requirements.txt` + `app.py` | - | | Python/Django | `manage.py` | `python manage.py collectstatic` | | Go | `go.mod` | `go build` | | Rust | `Cargo.toml` | `cargo build --release` | ## Quick Deploy ### Via Git Integration 1. Connect your Git provider in Temps dashboard 2. Select repository and branch 3. Temps auto-detects framework and deploys ### Via CLI ```bash # Install Temps CLI npm install -g @temps-sdk/cli # Login temps login # Deploy current directory temps deploy # Deploy with specific settings temps deploy --project my-app --branch main ``` ## Dockerfile Generation Temps auto-generates optimized Dockerfiles. For custom needs: ### Next.js (Standalone) ```dockerfile FROM node:20-alpine AS base FROM base AS deps WORKDIR /app COPY package*.json ./ RUN npm ci FROM base AS builder WORKDIR /app COPY --from=deps /app/node_modules ./node_modules COPY . . RUN npm run build FROM base AS runne...

Details

Author
gotempsh
Repository
gotempsh/temps
Created
10 months ago
Last Updated
today
Language
Rust
License
Apache-2.0

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

DevOps & Infrastructure Featured

temps

Manage, deploy, operate, and instrument applications with Temps. Use this skill whenever the user mentions Temps, `@temps-sdk/cli@0.1.34`, deploying or migrating an app to Temps, projects, environments, services, domains, backups, logs, monitoring, analytics, browser Performance Insights/Core Web Vitals, observability, error tracking, OpenTelemetry, tracing, session replay, or Temps Cloud. Also use it when preparing an application for production on Temps even if the user does not explicitly ask for the CLI. Route to focused references, proactively detect missing observability during create/link/deploy journeys, and use pinned `bunx` or `npx` CLI invocations with explicit target contexts.

655 Updated today
gotempsh
DevOps & Infrastructure Featured

temps-cli

Operate Temps through the pinned `@temps-sdk/cli` package with bunx or npx. Use when the user mentions Temps CLI, `@temps-sdk/cli`, a CLI command, or asks to deploy, configure, inspect, automate, or administer Temps from a terminal. Covers contexts, projects, deployments, environments, services, domains, monitoring, backups, telemetry, browser Performance Insights/Core Web Vitals, Cloud, platform administration, and read-only managed-data browsing. Apply the target-context, secret-handling, confirmation, and verification rules for every agentic CLI operation.

655 Updated today
gotempsh
DevOps & Infrastructure Featured

temps-best-practices

Best-practices reference for preparing and instrumenting applications on Temps. Covers the app runtime contract (`.temps.yaml` health, HOST/PORT, readiness, SIGTERM, replicas, migrations) and production observability (errors, traces, metrics, logs, analytics, privacy, sampling, cardinality, credential boundaries). Use whenever building or reviewing an app for Temps, configuring health checks, adding telemetry, diagnosing missing/noisy signals, or checking OTLP/Sentry/analytics ingestion. Triggers include "temps best practices", "prepare this app for Temps", ".temps.yaml health", "temps health check", "ignore health checks in otel", "temps observability", "wire up telemetry", and "instrument this app for temps". Prefer focused setup skills for a single SDK. Use temps-cli for executing deploy and resource-management commands.

655 Updated today
gotempsh