Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at

  • Peter Örneholm 6 posts 27 karma points
    Jan 05, 2015 @ 21:53
    Peter Ă–rneholm

    Using together with Courier

    I'm using your package in an environment where I use Courier to stage my website and there is an issue, but I'm not sure if it's that easy to solve. The "default" filesystemprovider store all files with a url that is relative to the current website, by default in /media/... So when media files are beeing transfered with Courier they will have the same url in the target environment (If I've understood it right).

    When using the Azure FileSystemProvider the URLs returned are absolute and pointing to the storage account specified in config. In my case I have one storage account for each environment I have Courier for. I was expecting Couirier to "recalcuate" the urls for the media items as part of the deployment, but it does not seem to do so. The result is that the urls will point to the storage account of the source website.

    Do you have any ideas of how to handle this?

  • Dirk Seefeld 122 posts 639 karma points
    Jan 06, 2015 @ 10:59
    Dirk Seefeld

    Hi Peter,

    sorry but this is beyond the scope of the FileSystemProvider. Once uploaded the URL or relative path is stored in the property "umbracoFile" (this is usally connected to the upload data type) of the media item. 

    One possible solution could be to extend Courier. At the moment I cannot provide you with more details about Courier. I just know it is highly customisable.


Please Sign in or register to post replies

Write your reply to: