21 lines
1.1 KiB
YAML
21 lines
1.1 KiB
YAML
|
decisions_log:
|
||
|
|
- question: >
|
||
|
|
Which image library backs JIT Generation, Glide or Intervention Image? (Same
|
||
|
|
question as `tech_stack`; flagging here too since this is where the
|
||
|
|
"Glide/Intervention" note actually lived.)
|
||
|
|
decision: Glide
|
||
|
|
rationale: >
|
||
|
|
Same decision/rationale as logged in `tech_stack.decisions_log`; kept in sync
|
||
|
|
across both sections.
|
||
|
|
- question: >
|
||
|
|
The glossary's "Storage Interface / Storage Abstraction" term lists GCP as an
|
||
|
|
example backend, but this section's "Storage Abstractions" list only names Local
|
||
|
|
Disk, S3, Nextcloud, and Linode Object-Storage. Should GCP be added to the
|
||
|
|
official supported-backends list here, or removed from the glossary example to
|
||
|
|
keep the two in sync?
|
||
|
|
decision: >
|
||
|
|
GCP has been removed from the glossary example (see `glossary`); it will not be
|
||
|
|
a supported storage backend at this time.
|
||
|
|
rationale: >
|
||
|
|
Keeps the glossary example list in sync with the actual supported backends
|
||
|
|
named here, rather than implying GCP support that doesn't exist.
|