Closed amancevice closed 2 years ago
hmm, try just packaging it with Claudia and then seeing what's actually in the package as a start. claudia pack
doesn't take a JSON file with ENV vars unfortunately.
$ NODE_ENV=production \
OUTPUT_DIR="./build" \
PUBLIC_DIR="./build/client" \
ASSETS_DIR="./build/client/assets" \
STATIC_BASE_URL="https://s3.us-east-1.amazonaws.com/S3_BUCKET/static/" \
BASE_URL="https://spoke.domain.com" \
ASSETS_MAP_FILE="assets.json" \
claudia pack --output ~/Desktop/
(this may also fail with the same error you got)
@amancevice did you ever figure this out? I'm doing some issue clean out and am unsure if this is still a problem
I did not—I haven't tried in some time, however. I know someone @ spoke was trying to get a terraform module together, but no idea where that stands.
Does creating a role (described here https://github.com/MoveOnOrg/Spoke/issues/1909) help with this issue? @amancevice @bchrobot
We migrated entirely to a Docker/Kubernetes based deploy a while ago and I'm not very familiar with this workflow anymore, sorry
closing -- lambda and deploys have changed
I am getting an error when trying to follow the docs on deploying Spoke to AWS Lambda. I have tried a couple different variations of the command but at its most-basic the command I ran was:
And the error:
I have run
npm run prod-build
before this stage so I do have the./build/server/server/index.js
file that is being required inlambda.js
.Full stacktrace: