Files
openfoodnetwork/spec
Maikel Linke 33d212d274 Gracefully deal with missing S3 config
I could have split this into several commits:

* DRY direct linking to images.
* Check S3 config before direct linking.
* Just check if service is public instead of relying on name.

Developers may copy a staging or production database or experiment with
S3 storage. But when the S3 config is missing then calling `service`
raises an ArgumentError due to a missing name.

Now we only try to call `service` if the S3 config is present.
2023-06-23 12:41:36 +10:00
..
2023-06-18 21:03:13 +02:00
2023-06-13 14:58:16 +01:00
2023-06-13 14:58:16 +01:00
2023-04-04 09:44:15 +09:00
2023-06-13 14:58:16 +01:00
2023-06-13 14:58:16 +01:00
2023-04-04 09:44:15 +09:00
2022-02-16 10:23:22 +11:00
2023-04-18 09:50:08 +10:00