Issues with filesystemproviders, virtual media folders, background threads and path mapping
Hi,
I have a website where the media is stored in a virtual directory (on the same disk) in order to be able to octopus-deploy the website without destroying media.
The same website also has a Hangfire schedule to update media.
It appears these scheduled updates do not put the media in the correct path, I assume because there is no http context to map the path correctly.
Issues with filesystemproviders, virtual media folders, background threads and path mapping
Hi, I have a website where the media is stored in a virtual directory (on the same disk) in order to be able to octopus-deploy the website without destroying media.
The same website also has a Hangfire schedule to update media.
It appears these scheduled updates do not put the media in the correct path, I assume because there is no http context to map the path correctly.
So what I will try is something like what is shown on this blog about How to Redirect the Umbraco Media Path to Another Location And is also mentioned in the Documentation for FileSystemProviders
Does anyone have any other options or advice?
Also: is the fact the path isn't mapping in a scheduled event (or probably any background thread) a bug I should report?
is working on a reply...