Single storage account with multiple containers

[creativesuspects]

I really love this package! I have a question though. Would it be possible to use a single Azure storage account with a separate container for each project? In that case the container name would obviously be something like media_projectname or whatever and not media. I noticed in uHangout episode #74 (https://youtu.be/5Qp-ZGaKFaY?t=7m45s) that Jeavon mentioned “there could potentially be some issues” when using a container that isn't named media? Of course we'd still want the Virtual Path Provider to translate the URLs to /media/* for each individual project.

[JimBobSquarePants]

Thanks!

I need to have a bit of a play around with configuration and see what limitations there are to what Umbraco expects to be sure. I'll have an experiment and let you know what I come up with.

[creativesuspects]

Awesome! Let me know what you find out.

[Jeavon]

I think this works ok actually, I have updated the Umbraco installer to support different containerName as it was not quite right before. I would love it if you tried it out, v0.5.1-beta-000068 or better :)

[creativesuspects]

Awesome! I'm working on another project right now, but I'll test the new package as soon as I can, and I'll let you know how it works. Is there anything in particular you'd like me to test?

On 25 Nov 2015, at 20:59, Jeavon notifications@github.com wrote:

I think this works ok actually, I have updated the Umbraco installer to support different containerName as it was not quite right before. I would love it if you tried it out, v0.5.1-beta-000068 or better :)

—
Reply to this email directly or view it on GitHub.

[Jeavon]

I should say it works for images only, requests for files that of course don't go through ImageProcessor do not directly. When you change the container name Umbraco will return the path to the file, e.g. my container name is "mediaMyProject" so the paths returned by Umbraco will be "/mediaMyProject/1011/myimage.jpg" the CloudSevice of ImageProcessor is happy to pick this up but if it's a PDF then it has to be requested from the media path e.g. "/media/1012/mypdf.pdf"

[Jeavon]

I think we need to adjust the pathPrefix parameter in this method https://github.com/JimBobSquarePants/UmbracoFileSystemProviders.Azure/blob/develop/src/UmbracoFileSystemProviders.Azure/FileSystemVirtualPathProvider.cs#L102 to read the prefix from FileSystemProviderManager

[JimBobSquarePants]

"Resharper seems drunk."

Classic commenting on my part there... That's a method I've been wanting to tinker with for a while as it affects #5

[perosb]

Maybe the internal Umbraco path should be "media"? regardless of the containerName?

That would also make it easier to move a database across environments which use different containerNames.

[creativesuspects]

Maybe the internal Umbraco path should be "media"? regardless of the containerName?

That would also make it easier to move a database across environments which use different containerNames.

I agree!

[oooshola]

Hey guys, has there been any solution to this? On the front end, things work find since I can always modify the src to be prefixed with "media." However, if i upload an image to the media section, its backoffice thumbnail is a broken image, since the thumbnail points to "/media_projectname/2059/example.jpg?width=500&mode=max"
EDIT:

I just realized what needs to happen. Several items need to have the same name. "media_projectname" can be anything, but it must be the same string in all of the below locations:

1. img src attributes in your templates: /media_projectname/2059/example.jpg?width=500&mode=max
2. In FileSystemProviders.config: <add key="containerName" value="media_projectname" /> However, the Provider alias is still exactly "media".
3. In cache.config: <setting key="SourceBlobContainer" value="media_projectname" />
4. In security.config: <service prefix="media_projectname" ... Also, <setting key="Host" value="http://youraccount.blob.core.windows.net/media_projectname/" />
5. In web.config (if using IIS Express):

<location path="media_projectname">
    <system.webServer>
      <handlers>
        <remove name="StaticFileHandler" />
        <add name="StaticFileHandler" path="*" verb="*" preCondition="integratedMode" type="System.Web.StaticFileHandler" />
      </handlers>
    </system.webServer>
  </location>

1. Put this line in an Umbraco ApplicationStarting event handler: Our.Umbraco.FileSystemProviders.Azure.FileSystemVirtualPathProvider.ConfigureMedia("media_projectname");

The last item is for pdfs. Visiting "/media_projectname/2059/example.pdf" would return a 404 otherwise, even in version 0.5.1.68-beta for me.

Thanks!

[Jeavon]

@oooshola Please try out the latest build v0.5.1-beta-000069 as I think I've fixed this so you shouldn't need your line in ApplicationStarting

[oooshola]

Yep @Jeavon this seems to do the trick. Thanks!

[Jeavon]

@oooshola great! I was thinking about seeing if I could get it to work keeping "media" as the virtual path but allowing a different container name, do you think it's worth exploring?