piolet
piolet
I created a PR #95 that goes in this direction, hoping that it makes sense for you
hey hey, everything is not so "ok" ;) by setting my root object, it's ok for the main index.html, i.e. for https://my-domain.com it's well redirected to https://my-domain.com/index.html but for a...
an other way, more simple, don't use directly the s3 for origin in cloud front, but his endpoint (for this, the S3 must be configured as static web host). to...
This my solution to avoid this limitation, for the moment. A patch with node module "patch-package" : ``` diff --git a/node_modules/serverless-lift/dist/src/constructs/aws/ServerSideWebsite.js b/node_modules/serverless-lift/dist/src/constructs/aws/ServerSideWebsite.js index d9aedaf..fef49f2 100644 --- a/node_modules/serverless-lift/dist/src/constructs/aws/ServerSideWebsite.js +++ b/node_modules/serverless-lift/dist/src/constructs/aws/ServerSideWebsite.js @@...
Oups, my patch failed with v.1.12 :(
> I ran tests from master right now, with node 17, and they are passing correctly 🤔 (not using Docker here) With node 17, npm install is blocked :/ Chelou,...
> hi @piolet, could you share the Dockerfile you use to run your tests ? I assume the test fixture path is not mounted properly in your container. Any reason...
Same result with node 16.14.2 on my environment directly :(
with a new computer, the tests work. It's confusing, but we can close this issue
fix with #283