Add s3 integration

Browse Source

Doing so has a number of benefits
- Overcome the 10Mb limit of the API gateway the lambdas have to go
through
- By storing the key as the hash of the code we can return previous
generated assets, i.e. caching
- cost, transfering assets into the bucket within the AWS ecosystem
is faster than return, and there fore the lambdas execute for less time
- Sets us up for the future as when generating artifacts for repos when
there is a change to master etc we want to store these assets somewhere
and s3 is an obvious choice
- Solved a weird CORS issue where I couldn't get CORS working with
binaryMediaTypes enabled, don't need binary types when dumping in s3

Resolves #316

...

This commit is contained in:

Kurt Hutten

2021-05-16 06:47:39 +10:00

parent 027b45e6c3

commit 315492a08a

17 changed files with 4766 additions and 980 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

2215

app/api/src/docker/cadquery/package-lock.json generated Normal file

File diff suppressed because it is too large Load Diff