Mercurial > gemma
view client/.env @ 3301:6514b943654e
Re-enable checking of gauge availability
This partly reverts rev. 1cb6676d1510, which removed this code in
favour of handling database errors later. The thinko in this was
that possibly many NtS messages for the same gauge would lead to
many errors for a single reason and the same amount of unnecessary
database round-trips. Checking whether the current user is allowed
to import data for a gauge now also handles sys_admin correctly
and the import stops with status unchanged if no such gauge is
available.
author | Tom Gottfried <tom@intevation.de> |
---|---|
date | Thu, 16 May 2019 17:22:33 +0200 |
parents | 3b36bb33f5b0 |
children | 33c398df5cb5 |
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 =