forked from External/greenlight
Improve container build: GRN2-156 (#582)
* Cache gems * Remove debug statement * Use postgress by default * Update sample.env
This commit is contained in:
committed by
Jesus Federico
parent
18214037c3
commit
ccbd46f045
15
sample.env
15
sample.env
@ -178,10 +178,21 @@ ENABLE_GOOGLE_CALENDAR_BUTTON=
|
||||
# ENABLE_SSL=true
|
||||
|
||||
# Database settings
|
||||
# Greenlight works out of the box with sqlite3, but if postgresql is required, especially for production
|
||||
# These variables should also be included.
|
||||
#
|
||||
# Greenlight may work out of the box with sqlite3, but for production it is recommended to use postgresql.
|
||||
# In such case, these variables must be included.
|
||||
#
|
||||
# DB_ADAPTER=postgresql
|
||||
# DB_HOST=postgres.example.com
|
||||
# DB_NAME=greenlight_production
|
||||
# DB_USERNAME=postgres
|
||||
# DB_PASSWORD=password
|
||||
#
|
||||
# Note that the example provided, works for deployments based on the docker-compose script wich is also included.
|
||||
# But should you need to use an external Postgres server, the right values for HOST, USERNAME and PASSWORD should be applied.
|
||||
#
|
||||
DB_ADAPTER=postgresql
|
||||
DB_HOST=db
|
||||
DB_NAME=greenlight_production
|
||||
DB_USERNAME=postgres
|
||||
DB_PASSWORD=password
|
||||
|
Reference in New Issue
Block a user