Mercurial > gemma

view client/.env @ 3705:7006b92c0334

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Handle updates (vs. historized and new versions) separately. We need this distinction as updated data currently can not be reviewed. More precisely: it can not be declined after review, as the old data is updated in place. The current exclusion from the review is a workaround and not meant to be the final solution. Note that there are additional minor problems, like the fact that the updated data is not counted as changed data for the import.
author Sascha Wilde <wilde@intevation.de>
date Wed, 19 Jun 2019 17:00:08 +0200
parents 33c398df5cb5
children 7a3ace19dc56
line wrap: on
line source

#Name of the application, e.g. displayed at login time
VUE_APP_TITLE=Waterway Monitoring system

#Backend URL
VUE_APP_API_URL=/api/
VUE_BACKEND_API_URL=http://gemma-backend:8000

#Path of vendored images is copied during a webpack build
VUE_APP_VENDOR_IMG_PATH=

#Logos to be potentially loaded by the SPA. Can be left blank.
VUE_APP_SECONDARY_LOGO_URL=
VUE_APP_LOGO_FOR_PDF_URL=
VUE_APP_SILENCE_TRANSLATIONWARNINGS =

#Url of user manual
VUE_APP_USER_MANUAL_URL=