-
Notifications
You must be signed in to change notification settings - Fork 1
/
.env.travis
175 lines (153 loc) · 4.95 KB
/
.env.travis
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
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
#
# Database
#
DB_DRIVER="postgres"
DB_HOST="localhost"
DB_NAME="apt_registry_travis"
DB_USER="travis"
DB_PASSWORD=""
DB_PORT=5433 # yes, non-standard port on travis
DB_USE_SSL=false
#
# Keys for cookie encryption
#
# Use single quotes on this so that viper does not
# try to interpret dollar signs as vars.
#
COOKIE_HASH_KEY='ouU-0s;}mC*+$~0JR>79J}&z@xplP<43zxP#StHU$}D(<;2p2PW:RAEli}a6'
COOKIE_BLOCK_KEY='DpRI83tgJq4LiA9tRkePPe7txcjN1fZh'
#
# Session Cookie - max age is in seconds (43,200 = 12 hours)
#
COOKIE_DOMAIN="localhost"
SESSION_MAX_AGE=43200
SESSION_COOKIE_NAME="aptrust_session"
FLASH_COOKIE_NAME="aptrust_flash"
PREFS_COOKIE_NAME="aptrust_prefs"
#
# Serve cookies only via https?
# Set this to true outside of the dev and test environments.
#
HTTPS_COOKIES=false
#
# NSQ_URL is the URL for pushing items into work queues.
#
# To queue an item, we post a WorkItem ID to {NSQ_URL}/pub?topic=topic_name
# The WorkItem ID is the body of the POST request.
#
# Note that NSQ typically runs on port 4151, and it runs a lookup daemon
# on port 4161 and a Web UI on port 4171. We just need 4151 for pushing
# items into queues.
#
NSQ_URL='http://localhost:4151'
#
# Secret key required to perform batch deletions.
#
BATCH_DELETION_KEY="00000000-0000-0000-0000-000000000000"
#
# EMAIL_SERVICE_TYPE should be "SES" if we have access to SES endpoints
# or "SMTP" if we're operating on a private subnet that can't access SES.
#
EMAIL_SERVICE_TYPE="SES"
#
# MAINTENANCE_MODE indicates whether Registry is in maintenance mode.
# When this is true, ALL requests will result in a "503 - Service Unavailable"
# response with a message saying the system is undergoing maintenance.
# Also, when this is true, the Registry's cron jobs will not run.
# We typically turn this on when we're doing a database migration and we
# don't want Registry writing anything to the database.
#
MAINTENANCE_MODE=false
#
# Two-Factor auth settings.
#
# If you have valid AWS credentials in ~/.aws/credentials
# and valid region in ~/.aws/config, set this to true to
# be able to send SMS messages for two-factor auth.
#
# For two factor to work, you'll need to set the following
# environment vars. We don't set these in the .env file for
# security reasons.
#
# AWS_ACCESS_KEY_ID=<your key id>
# AWS_SECRET_ACCESS_KEY=<your secret key>
# AWS_REGION=us-east-1
#
# Or you can set vars AWS_SES_USER and AWS_SES_PWD
# to supply specific credentials for both SES and SNS
# services. These settings, if provided, will override
# the access key settings for both SES and SNS.
#
ENABLE_TWO_FACTOR_SMS=false
#
# How to connect to SNS to send out 2-factor text messages?
#
SNS_ENDPOINT=""
AWS_SNS_USER=""
AWS_SNS_PWD=""
# If you have valid Authy keys, set this to true.
# You'll need to set the following env variable:
#
# AUTHY_API_KEY=<your key>
#
ENABLE_TWO_FACTOR_AUTHY=false
# How long should one-time passwords sent via text/SMS last?
# Use Go duration format. Examples:
# "60s" = 60 seconds
# "5m" = 5 minutes
# "2h" = 2 hours
OTP_EXPIRATION="15m"
# If email is enabled, we will send alerts, password reset notices, etc.
# via email. We want this to be true in production and demo, and maybe
# in staging as well. For dev, test, travis, it should probably be false
# to avoid spamming people (especially during automated testing).
#
# Note that, like SMS, the SES email service requires a region. Typically,
# that's set alongside the access key info in ~/.aws/config, but you can
# add it to this file if you like.
EMAIL_ENABLED=false
# This will be the from and reply-to address in emails generated by the
# Registry.
EMAIL_FROM_ADDRESS="[email protected]"
# REDIS_DEFAULT_DB is the number of the Redis DB in which preservation
# services keeps its data. This should be 0 in most cases.
REDIS_DEFAULT_DB= 0
# REDIS_PASSWORD is the password requried to connect to the Redis
# server. In dev and test, this should be an empty string.
REDIS_PASSWORD=""
# REDIS_URL is the URL of the Redis server in the format "host:port".
# The default port is 6379. For dev and test, this should be localhost:6379.
REDIS_URL="localhost:6379"
#
# The RETENTION_MINIMUM vars describe the minimum number of days
# an item must be kept in preservation storage before a depositor
# can delete them. Minimum retention period varies by storage type.
# And yes, Standard is zero. You can delete from Standard at any time.
#
RETENTION_MINIMUM_GLACIER=90
RETENTION_MINIMUM_GLACIER_DEEP=180
RETENTION_MINIMUM_WASABI=90
RETENTION_MINIMUM_STANDARD=0
#
# Logging Levels, from https://github.com/rs/zerolog/blob/master/log.go
#
# -1 Trace
# 0 Debug
# 1 Info
# 2 Warn
# 3 Error
# 4 Fatal
# 5 Panic
# 6 None
# 7 Disabled
#
# If LOG_CALLER is set to true, we will log the filename and line number
# from which the logger was called.
#
# The logger will always log to LOG_FILE. If you want to log to the console
# as well, set LOG_TO_CONSOLE to true. This is useful in development.
LOG_FILE="./registry_test.log"
LOG_LEVEL=0
LOG_CALLER=false
LOG_TO_CONSOLE=false
LOG_SQL=false