-
Notifications
You must be signed in to change notification settings - Fork 112
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
server-side-website with additional S3 Origin behaviour #325
base: master
Are you sure you want to change the base?
server-side-website with additional S3 Origin behaviour #325
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome, that looks like a great idea that will benefit many! (the "/uploads/" example is very common)
I added some suggestions inline. Could you also add some tests? This is a large feature so we want to make sure it is covered.
Hi, just bumping here regarding my last comment: I think the only thing missing here for a merge are tests? Especially since you discovered plenty of edge cases, maintaining this feature sounds like it will be quite some effort, so the tests will help minimize the effort 😅 |
Sure thing, @robchett just added these now :) |
@mnapoli Just wondering if there is a plan in mind for the next release and will it include this PR? If there's anything we can help with, let us know. Thanks. |
Hey @fredericbarthelet, @mnapoli Any chance this could be reviewed / merged if you're happy with the change & tests added here please? |
Co-authored-by: Matthieu Napoli <matthieu@mnapoli.fr>
the same bucket twice to different paths
14993f6
to
fba77bd
Compare
Hope that this will be finally merged. |
Aran Reeks (@aran112000) while It is not being approved, how can we use this? will uploaded files to the bucket be removed on the next deployment? |
Feel free to use my fork of Lift, we use this on production on a number of sites successfully. It doesn't clear any assets from other buckets on deployment. They're just added as origins to your Cloudfront distributions. @mnapoli - is it possible to complete the review and get this merged, please? |
This adds support to create additional CloudFront Origins & Behaviours so you can map additional paths to alternative, existing S3 buckets.
Includes updated documentation to show how this can be used.