-
Notifications
You must be signed in to change notification settings - Fork 71
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
Add key prefix as a configuation option #103
Comments
@bubenkoff thanks for raising that point. Can you please suggest a suitable solution? I haven't faced that issue before so any details you can share are much appreciated! |
I'm actually facing the same sort of problem on an S3/CloudFront environment as described by @bubenkoff , where I have just one bucket, hosting multiple apps' assets. At the moment I use just one app on the CDN, so I'm good having a public folder on the bucket's root directory, but this could potentially display the package issue if I decide to use the package on the other apps since, in a Laravel environment, you most likely always push content from the public directory, potentially overwriting every apps assets.
I fear though that these edits could "break stuff" (very technical term), as you are most likely not allowed to add a custom key to Apolgies if I've written something outrageous or haven't formatted the answer properly, but I'm very inexperienced with GitHub's issue tracker. |
@thtg88 Thanks for the details. I'm just afraid that would require too much config in the simple case where you only have one bucket per app. I always lean towards simplicity when it comes to config. I was thinking whether |
@Mulkave Forgot to mention I tried that, unfortunately it throws an exception as the forward-slash '/' character gets urlencoded. I'm not at my PC right now but I can provide the Exception details if needed. |
@thtg88 sure some more details on the exception would help. I'm also not able to try that atm. |
Hi @Mulkave , apologies for the delay. You can find the exception message below:
Should you need any other details, please let me know. |
@Mulkave, Very actual problem! Maybe I propose PR for this? |
I'm currently running into this issue. It would be good to have this feature available. The main reason is we have different branches being staged that need different CDN assets. |
It's not uncommon to have single s3 bucket for multiple applications, connected to a single cloudfront domain, separated just by a key prefix, example:
ATM there's no easy way to implement this with this very nice package
thanks!
The text was updated successfully, but these errors were encountered: