-
Notifications
You must be signed in to change notification settings - Fork 1
Expand file tree
/
Copy path.env.example
More file actions
87 lines (68 loc) · 3.04 KB
/
.env.example
File metadata and controls
87 lines (68 loc) · 3.04 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
79
80
81
82
83
84
85
86
87
# Database Handler CLI - Environment Configuration
#
# This file shows how to configure database connections for the CLI.
# Copy this file to `.env` and fill in your actual database credentials.
#
# IMPORTANT: Never commit the `.env` file to version control!
# ============================================================================
# Database Connections
# ============================================================================
#
# Format: DATABASE_URL=postgresql://user:password@host:port/database
#
# Add a comment above each DATABASE_URL to give it a friendly name.
# This name will appear in the interactive database selection menu.
#
# You can define multiple database connections below.
# Docker Demo Database
DATABASE_URL=postgresql://postgres:password@localhost:5432/db_handler_demo
# Production Database
DATABASE_URL=postgresql://user:password@localhost:5432/prod_db
# Staging Database
DATABASE_URL=postgresql://user:password@localhost:5432/staging_db
# Development Database
DATABASE_URL=postgresql://user:password@localhost:5432/dev_db
# Local Test Database
DATABASE_URL=postgresql://postgres:postgres@localhost:5432/test_db
# If you don't want to add comments in your `.env` file,
# you can simply give a much more explicit name to your DATABASE_URL like :
DATABASE_URL_DEV=postgresql://user:password@localhost:5432/dev_db
DATABASE_URL_PROD=postgresql://user:password@localhost:5432/prod_db
DATABASE_URL_DEMO=postgresql://user:password@localhost:5432/demo_db
# ============================================================================
# SSL Configuration (Optional)
# ============================================================================
#
# For databases requiring SSL, add one of the following to your connection string:
# - ?sslmode=require
# - ?ssl=true
#
# Example:
# DATABASE_URL=postgresql://user:password@host:5432/db?sslmode=require
# ============================================================================
# Cloud Provider Examples
# ============================================================================
# AWS RDS
# DATABASE_URL=postgresql://user:password@mydb.abc123.us-east-1.rds.amazonaws.com:5432/mydb
# Heroku Postgres
# DATABASE_URL=postgres://user:password@ec2-xx-xxx-xx-xxx.compute-1.amazonaws.com:5432/dbname
# Supabase
# DATABASE_URL=postgresql://postgres:password@db.xxxxx.supabase.co:5432/postgres
# Railway
# DATABASE_URL=postgresql://postgres:password@containers-us-west-xx.railway.app:5432/railway
# Render
# DATABASE_URL=postgresql://user:password@xxx-postgres.render.com/dbname
# ============================================================================
# Notes
# ============================================================================
#
# - Make sure your database user has appropriate permissions:
# - SELECT (for dumps and listing)
# - INSERT (for imports)
# - DELETE (for truncate)
# - DROP (for drop operations)
#
# - For production databases, consider using read-only credentials
# for dump operations to prevent accidental data modification.
#
# - Always test with a non-production database first!