juicebox-multi-env-setup
Configure Juicebox multi-environment setup. Use when setting up dev/staging/production environments, managing per-environment configurations, or implementing environment isolation. Trigger with phrases like "juicebox environments", "juicebox staging", "juicebox dev prod", "juicebox environment setup".
- License 许可
- MIT
- 最近更新
- 2026-11-15
- Stars
- ★ 2.0k
- Forks
- 233
01 前言 Front Matter
- name
- juicebox-multi-env-setup
- author
- Jeremy Longshore <jeremy@intentsolutions.io>
- license
- MIT
- version
- 1.0.0
- description
- Configure Juicebox multi-environment setup. Use when setting up dev/staging/production environments, managing per-environment configurations, or implementing environment isolation. Trigger with phrases like "juicebox environments", "juicebox staging", "juicebox dev prod", "juicebox environment setup".
- allowed-tools
- Read, Write, Edit, Bash(kubectl:*), Bash(curl:*)
03 SKILL.md 正文
Juicebox Multi-Environment Setup
Overview
Configure Juicebox across development, staging, and production environments with proper isolation and security.
Prerequisites
- Separate Juicebox accounts or API keys per environment
- Secret management solution (Vault, AWS Secrets Manager, etc.)
- CI/CD pipeline with environment variables
- Environment detection in application
Environment Strategy
| Environment | Purpose | API Key | Rate Limits | Data |
|---|---|---|---|---|
| Development | Local dev | Sandbox | Relaxed | Mock/Test |
| Staging | Pre-prod testing | Test | Production | Subset |
| Production | Live system | Production | Full | Real |
Instructions
Step 1: Environment Configuration
// config/environments.ts
interface JuiceboxEnvConfig {
apiKey: string;
baseUrl: string;
timeout: number;
retries: number;
sandbox: boolean;
}
const configs: Record<string, JuiceboxEnvConfig> = {
development: {
apiKey: process.env.JUICEBOX_API_KEY_DEV!,
baseUrl: 'https://sandbox.api.juicebox.ai',
timeout: 30000,
retries: 1,
sandbox: true
},
staging: {
apiKey: process.env.JUICEBOX_API_KEY_STAGING!,
baseUrl: 'https://api.juicebox.ai',
timeout: 30000,
retries: 2,
sandbox: false
},
production: {
apiKey: process.env.JUICEBOX_API_KEY_PROD!,
baseUrl: 'https://api.juicebox.ai',
timeout: 60000,
retries: 3,
sandbox: false
}
};
export function getConfig(): JuiceboxEnvConfig {
const env = process.env.NODE_ENV || 'development';
const config = configs[env];
if (!config) {
throw new Error(`Unknown environment: ${env}`);
}
if (!config.apiKey) {
throw new Error(`JUICEBOX_API_KEY not set for ${env}`);
}
return config;
}
Step 2: Secret Management by Environment
// lib/secrets.ts
import { SecretsManager } from '@aws-sdk/client-secrets-manager';
const secretPaths: Record<string, string> = {
development: 'juicebox/dev/api-key',
staging: 'juicebox/staging/api-key',
production: 'juicebox/prod/api-key'
};
export async function getApiKey(): Promise<string> {
const env = process.env.NODE_ENV || 'development';
// In development, allow env var fallback
if (env === 'development' && process.env.JUICEBOX_API_KEY_DEV) {
return process.env.JUICEBOX_API_KEY_DEV;
}
// Production environments must use secret manager
const client = new SecretsManager({ region: process.env.AWS_REGION });
const result = await client.getSecretValue({
SecretId: secretPaths[env]
});
return JSON.parse(result.SecretString!).apiKey;
}
Step 3: Environment-Aware Client Factory
// lib/client-factory.ts
import { JuiceboxClient } from '@juicebox/sdk';
import { getConfig } from '../config/environments';
import { getApiKey } from './secrets';
let clientInstance: JuiceboxClient | null = null;
export async function getJuiceboxClient(): Promise<JuiceboxClient> {
if (clientInstance) return clientInstance;
const config = getConfig();
const apiKey = await getApiKey();
clientInstance = new JuiceboxClient({
apiKey,
baseUrl: config.baseUrl,
timeout: config.timeout,
retries: config.retries
});
// Add environment-specific middleware
if (process.env.NODE_ENV === 'development') {
clientInstance.use(logRequestsMiddleware);
}
return clientInstance;
}
Step 4: Kubernetes ConfigMaps
# k8s/base/configmap.yaml
apiVersion: v1
kind: ConfigMap
metadata:
name: juicebox-config
data:
JUICEBOX_TIMEOUT: "30000"
JUICEBOX_RETRIES: "3"
---
# k8s/overlays/development/configmap.yaml
apiVersion: v1
kind: ConfigMap
metadata:
name: juicebox-config
data:
JUICEBOX_BASE_URL: "https://sandbox.api.juicebox.ai"
JUICEBOX_SANDBOX: "true"
---
# k8s/overlays/staging/configmap.yaml
apiVersion: v1
kind: ConfigMap
metadata:
name: juicebox-config
data:
JUICEBOX_BASE_URL: "https://api.juicebox.ai"
JUICEBOX_SANDBOX: "false"
---
# k8s/overlays/production/configmap.yaml
apiVersion: v1
kind: ConfigMap
metadata:
name: juicebox-config
data:
JUICEBOX_BASE_URL: "https://api.juicebox.ai"
JUICEBOX_SANDBOX: "false"
JUICEBOX_TIMEOUT: "60000"
Step 5: Environment Guards
// lib/environment-guards.ts
export function requireProduction(): void {
if (process.env.NODE_ENV !== 'production') {
throw new Error('This operation is only allowed in production');
}
}
export function preventProduction(): void {
if (process.env.NODE_ENV === 'production') {
throw new Error('This operation is not allowed in production');
}
}
// Usage
async function resetTestData(): Promise<void> {
preventProduction();
await db.profiles.deleteMany({});
}
async function sendBulkOutreach(): Promise<void> {
requireProduction();
// ... production-only logic
}
Environment Checklist
## Environment Setup Verification
### Development
- [ ] Sandbox API key configured
- [ ] Mock data available
- [ ] Debug logging enabled
- [ ] Rate limits relaxed
### Staging
- [ ] Test API key configured
- [ ] Production-like data subset
- [ ] Monitoring enabled
- [ ] Matches production config
### Production
- [ ] Production API key in secret manager
- [ ] All guards enabled
- [ ] Monitoring and alerting
- [ ] Backup and recovery tested
Output
- Environment-specific configurations
- Secret management per environment
- Kubernetes overlays
- Environment guards
Resources
Next Steps
After environment setup, see juicebox-observability for monitoring.
04 同仓库更多 Skills
theme-factory
Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors/fonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.
web-artifacts-builder
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
neuropixels-analysis
Neuropixels neural recording analysis. Load SpikeGLX/OpenEphys data, preprocess, motion correction, Kilosort4 spike sorting, quality metrics, Allen/IBL curation, AI-assisted visual analysis, for Neuropixels 1.0/2.0 extracellular electrophysiology. Use when working with neural recordings, spike sorting, extracellular electrophysiology, or when the user mentions Neuropixels, SpikeGLX, Open Ephys, Kilosort, quality metrics, or unit curation.
skill-creator
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
notebooklm
Use this skill to query your Google NotebookLM notebooks directly from Claude Code for source-grounded, citation-backed answers from Gemini. Browser automation, library management, persistent auth. Drastically reduced hallucinations through document-only responses.