We shouldn't misuse TESTING=True (intended for running the test suite) for our staging deployment just because we want to use the real FAS instead of a fake FAS. Make it better configurable (e.g. FAS=auto/True/False for autodetection of production/development, or force enabled/disabled, where disabled means fake FAS).
TESTING=True
FAS=auto/True/False
After this is done, tell @frantisekz to adjust the staging config.
Issue tagged with: next
Metadata Update from @kparal: - Issue assigned to kparal
PR is in #189
Commit e5372509 fixes this issue
I'm going to keep this open, until we deploy a new version to staging and update the config in there.
Metadata Update from @kparal: - Issue status updated to: Open (was: Closed)
This is now updated in staging and seems to work, yay. Thanks @frantisekz .
Metadata Update from @kparal: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
This issue has been migrated to Fedora Forge: https://forge.fedoraproject.org/quality/blockerbugs/issues/182
Please continue any further discussion there.
Log in to comment on this ticket.