Dec 15, 2011 at 9:18 AM
Edited Dec 15, 2011 at 2:50 PM
If you upload random files to wp-content, like a plugin, you bypass both the storage plugin and the sync plugin (when using scaffold defaults).
Thanks for your response.
So do I understand it correctly that ONLY media files (such as images, document files, videos) that are uploaded through the dashboard will be synced on my Blob storage through the storage plugin (http://wordpress.org/extend/plugins/windows-azure-storage/)
But any other data uploaded through the dashboard (such as themes and plugins) are stored ONLY locally on the VM and won't be synced to the blob storage?
If my understanding from above is correct, it is reassuring to see that the media won't be lost, but its also a bit concerning, as if the VM crashes for any reason and gets restarted, I would loose all the plugins and theme settings.
I have tried to emulate this situation last night by logging into the Azure Dashboard, clicked on the WebRole containing the WordPress scaffolding and clicked on Reboot.
After the reboot; interesting enough my textfile on VM's desktop survived it. But the entire directory of my WordPress installation was deleted and reinstalled since none of the plugins and themes in the wp-content folder was available any longer. I
can also confirm this even further as I had received an email from my PowerShell script that runs as a StartUp task whenever the package gets re-populated.
It seems that the only difference between Azure dashboard's 'Reimage' and 'Reboot' is that the former wipes everything off, while Reboot wipes only drive E: off where the sites are stored.
I will test again tonight with a new fresh installation, apply a custom theme and add some plugins, thereafter I will reboot the image to see if they are lost for good or not.
Ben, It seems I have found partially the answer to my question: http://social.msdn.microsoft.com/Forums/en-AU/windowsazuredevelopment/thread/3cd21ac6-aeb6-442b-af89-ae913946b3ba
In this case there is really no way around it but to sync the entire wp-content with my blob storage. A WordPress installation grown with time, you add new plugins and features, and you don't want to loose them whenever the data center sees fir to
reboot your instance (as its normal in cloud systems)
You have mentioned previously I should be looking into ServiceConfiguration.cscfg and target the entire wp-content. I will check this out tonight.
I have found the solution with a nice explanation: https://github.com/Interop-Bridges/Windows-Azure-File-System-Durability-Plugin # Readme
By the look of it if I comment out this line:
It won't just sync that specified file but would rather sync the entire folder specified in this line:
<Setting name="FileSystemDurabilityPlugin.FileNameIncludesToSync" value="" /> <!-- Optional: To sync specific files only -->
<Setting name="FileSystemDurabilityPlugin.LocalFolderToSync" value="*****" /> <!-- Relative path to approot -->
That site also warns about the possibility of higher costs incurred when doing this. But as it would only sync and copy the files over that have actually changed, traffic shouldn't be too bad.
Let see.. :)