This repository was archived by the owner on Apr 7, 2026. It is now read-only.
forked from GeospatialResearch/Digital-Twins
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy path.env.template
More file actions
40 lines (32 loc) · 1.54 KB
/
.env.template
File metadata and controls
40 lines (32 loc) · 1.54 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
# Copy this file and store it as ".env" and fill in the required environment variables.
DEBUG_TRACEBACK=False
TEST_DATABASE_INTEGRATION=True
POSTGRES_HOST=localhost
POSTGRES_PORT=5431
POSTGRES_DB=db
POSTGRES_USER=postgres
POSTGRES_PASSWORD=
MESSAGE_BROKER_HOST=localhost
GEOSERVER_HOST=http://localhost
GEOSERVER_PORT=8088
GEOSERVER_ADMIN_NAME=admin
GEOSERVER_ADMIN_PASSWORD=geoserver
BACKEND_HOST=http://localhost
BACKEND_PORT=5000
WWW_PORT=3001
CESIUM_ACCESS_TOKEN=
# for NewZeaLiDAR
# directory name for source LiDAR data from OpenTopography, parent dir is DATA_DIR
LIDAR_DIR=lidar
# directory name for output hydrological conditioned DEM data processed by GeoFabrics, parent dir is DATA_DIR
DEM_DIR=hydro_dem
# land polygon required by GeoFabrics, the parent dir is DATA_DIR, if you don't use GeoFabrics package, you can leave it blank
LAND_FILE=
# base instructions dictionary for NewZeaLiDAR (and GeoFabrics, if needed), indispensable input file, the parent dir is project root dir
INSTRUCTIONS_FILE=./instructions.json
# The following variables are used only for local development and debugging.
# See the wiki for instuctions on how to use them. <https://github.com/GeospatialResearch/Digital-Twins/wiki/Running-the-code-in-development-environment>
DATA_DIR=U:/Research/FloodRiskResearch/DigitalTwin/stored_data
DATA_DIR_MODEL_OUTPUT=U:/Research/FloodRiskResearch/DigitalTwin/stored_data/model_output
DATA_DIR_GEOSERVER=U:/Research/FloodRiskResearch/DigitalTwin/stored_data/geoserver
FLOOD_MODEL_DIR=U:/Research/FloodRiskResearch/DigitalTwin/BG-Flood/BG_Flood_v0-9