bot/WeatherTool
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Split ENABLE_LEGACY_PROVIDER_JOBS into independent FTP/HARMONIE flags

Browse Source 
Real LVGMC FTP credentials arrived today; real DMI HARMONIE
credentials haven't. The combined flag would have enabled both the
moment FTP's were ready, crash-looping the app on HARMONIE's still-
placeholder values via parMapN — caught this before it happened
(the Grib job was ~15 min from its first scheduled run). Split into
ENABLE_LVGMC_FTP_JOBS and ENABLE_HARMONIE_JOBS so each provider can
be enabled independently as its own credentials become real.
This commit is contained in:
b0txec
2026-08-23 21:32:11 +03:00
parent 3315f00fb1
commit 3eddf95008
8 changed files with 64 additions and 24 deletions
Download Patch File Download Diff File Expand all files Collapse all files
deploy/vps/compose.yml
+4 -3
View File
@@ -32,11 +32,12 @@ services:
POSTGRES_PASSWORD: ${POSTGRES_PASSWORD}
POSTGRES_HOST: postgres
ENABLE_SCHEDULED_JOBS: "true"
ENABLE_LEGACY_PROVIDER_JOBS: "false"
ENABLE_LVGMC_FTP_JOBS: "false"
ENABLE_HARMONIE_JOBS: "false"
DEBUG: "false"
# The legacy FTP/HARMONIE provider services are still constructed at
# startup even though ENABLE_LEGACY_PROVIDER_JOBS keeps their scheduled
# jobs off, so inert values are required until real credentials exist.
# startup even though these flags keep their scheduled jobs off, so
# inert values are required until each one's real credentials exist.
LVGMC_USER: disabled
LVGMC_PASSWORD: disabled
LVGMC_URL: https://invalid.local/