-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deploy doesn't work #4
Comments
s3 bucket names need to be unique, so you need to alter the name of the bucket 'nuxt-serverless-at-edge' to something unique, you will need to alter that name for every occurrence in the serverless.yaml file |
Yes, I know it and put unique bucket name, but still it doesn't work. |
Are you still getting a deploy error or and error when requesting the Cloudfront url? |
After I change "before:deploy:deploy" on "after:deploy:deploy" I start get error when requesting to the Cloudfront url. I used your example from this repo, just changed bucketname and deploy queue |
Hi, I tried deploy your example, and get this errors:
` before:deploy:deploy:
To this:
after:deploy:deploy: - aws s3 cp --recursive ./.nuxt/dist/client/ s3://nuxt-serverless-at-edge/_nuxt/ --cache-control "max-age=31536000,public,immutable" - aws s3 cp --recursive ./static/ s3://nuxt-serverless-at-edge/ --exclude "README.md" --cache-control "max-age=31536000,public,immutable"
ERROR
The request could not be satisfied.
The Lambda function returned an invalid request or response to CloudFront.
Generated by cloudfront (CloudFront)
Please, can you update configuration? Thanks!
The text was updated successfully, but these errors were encountered: