-
Notifications
You must be signed in to change notification settings - Fork 13
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
Implementation for Umbraco 9 #13
Comments
Looking to do the same but not for a few weeks yet, might have a bash at a V9 version of this. |
Did anyone look at this yet? |
I have been looking at it before Christmas need to spend some more time on it! |
Hi there - has anyone had any more luck with a v9 version? |
Hi Warren, I've done a lot of work on this now. A modification has gone into ImageSharp.Web which has been merged a release needs to happen on that. Once that is done Umbraco needs a modification and upgrade to use the latest version of ImageSharp.Web. I can then release the FileProvider. If you're happy to work with pre-release versions and modify/hack Umbraco I can send details |
Yes please that would be great! |
Hey @andyfelton-equatedigital Any news on this? |
I've made an early prototype for Umbraco V9 based on https://github.com/umbraco/Umbraco.StorageProviders available here: https://github.com/DennisGlindhart/Umbraco.StorageProviders.S3 |
OK got around to writing up my notes - sorry for the delay this is now available on my repository https://github.com/andyfelton-equatedigital/Umbraco.StorageProviders.AWSS3. Note due to changes required on ImageSharp.Web you'll need the non-released version and that has breaking changes which will need an update to Umbraco. Details are available on the project readme under usage - any problems give us a shout. |
I cheated a bit when the new Version 9.3 parameter of "UmbracoMediaPhysicalRootPath" came along. I've pointed this to a shared Drive/folder which is served from S3. Seems to be working well so far. |
I have moved a site to Umbraco 9 from Umbraco 8 and would like to continue with S3 for our media - is anybody working on a version of the S3 file provider if not I'll start looking at a provider.
The text was updated successfully, but these errors were encountered: