Repository navigation
Expand file tree
/
Copy path.env.example
More file actions
78 lines (65 loc) · 3.57 KB
/
Copy path.env.example
File metadata and controls
78 lines (65 loc) · 3.57 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
# Environment Variables Template
# Copy this file to .env.local for local development (non-Docker)
# Or use .env.dev.example / .env.prod.example for Docker Compose setups
# Database Configuration
# For local development: use localhost
# For Docker Compose: use the service name (e.g., 'postgres')
DATABASE_URL="postgresql://postgres:postgres@localhost:5432/multisig"
DIRECT_URL="postgresql://postgres:postgres@localhost:5432/multisig"
# Node Environment (development, test, or production)
NODE_ENV="development"
# JWT Secret (minimum 32 characters required)
# Generate a secure secret: openssl rand -base64 32
JWT_SECRET="your-jwt-secret-minimum-32-characters-long"
# Pinata IPFS Configuration
# Get your JWT token from https://app.pinata.cloud/
PINATA_JWT="your-pinata-jwt-token"
# Optional: dedicated Pinata IPFS gateway origin (e.g. https://<id>.mypinata.cloud).
# IPFS reads resolve through /api/ipfs/resolve, which tries this gateway first
# (our pinned content) before falling back to public gateways, and new uploads
# return a URL on this gateway instead of the frequently-504ing public ipfs.io.
# NEXT_PUBLIC_PINATA_GATEWAY_URL="https://your-gateway.mypinata.cloud"
# GitHub Personal Access Token
# Create one at https://github.com/settings/tokens
# GITHUB_TOKEN="your-github-token" (Optional - for GitHub issue creation)
# Blockfrost API Keys
# Get your API keys from https://blockfrost.io/
# These are client-side variables (exposed to browser)
NEXT_PUBLIC_BLOCKFROST_API_KEY_MAINNET="your-blockfrost-mainnet-api-key"
NEXT_PUBLIC_BLOCKFROST_API_KEY_PREPROD="your-blockfrost-preprod-api-key"
# Snapshot Auth Token
# Used to authenticate the balance snapshot batch endpoint
# SNAPSHOT_AUTH_TOKEN="your-snapshot-auth-token"
# Canonical public URL of the deployment.
# Used for bot setup guide URLs and SEO: canonical tags, Open Graph / Twitter
# URLs, robots.txt and the sitemap. Defaults to the production domain when unset;
# set this on local, preview or self-hosted environments so links point at the right origin.
# NEXT_PUBLIC_SITE_URL="https://multisig.meshjs.dev"
# Optional: Skip environment validation during builds
# Useful for Docker builds where env vars are set at runtime
# SKIP_ENV_VALIDATION=true
# Optional: NextAuth Configuration (if using NextAuth.js)
# NEXTAUTH_SECRET="your-nextauth-secret"
# NEXTAUTH_URL="http://localhost:3000"
# Optional: Discord Integration (if using Discord features)
# DISCORD_CLIENT_ID="your-discord-client-id"
# DISCORD_CLIENT_SECRET="your-discord-client-secret"
# DISCORD_BOT_TOKEN="your-discord-bot-token"
# DISCORD_GUILD_ID="your-discord-guild-id"
# Optional: Email notifications via Resend
# RESEND_API_KEY="re_..."
# EMAIL_FROM="Mesh Multisig <notifications@your-domain.example>"
# EMAIL_REPLY_TO="support@your-domain.example"
# Optional: override notification email links. Required for localhost links when
# using `next start` locally (NODE_ENV is production). Defaults to
# http://localhost:3000 in `next dev` and the production site URL otherwise.
# NOTIFICATION_LINK_BASE_URL="http://localhost:3000"
# NOTIFICATION_DRAIN_SECRET="your-notification-drain-secret"
# NOTIFICATIONS_EMAIL_ENABLED="false"
# Optional: OAuth 2.1 issuer for the MCP endpoint (/api/mcp)
# Canonical origin of the authorization server. Access tokens carry it as `iss`,
# and the /.well-known discovery documents are built from it. Falls back to
# NEXT_PUBLIC_SITE_URL; set this only if the issuer must differ from the site
# origin. In non-production it falls back to the request host, so a local
# `next start` on any port works without setting anything.
# OAUTH_ISSUER_URL="https://multisig.meshjs.dev"