Rollbacks might be useful for some purposes, but I’m not going to need them here:Īnd we’re done! Except that we have no deployments: Once this is done, the Dropbox client lets us know there’s something new to look at:Īnd sure enough, I now have an “Apps” folder with an “Azure” folder within it:īack in the browser, now that the OAuth magic is complete I get a folder named after the website which is then also created in the image above within that Azure directory: The Dropbox website challenges for a logon: So into the deployment settings:Īfter choosing “Dropbox”, it’ll do some auth to make sure it has access to your content: Now this is slightly misleading because as you’ll see soon, this process won’t really be “continuous” deployment, but this is where we’ll kick things off from. Once the site is there (I called mine “troyhuntfiles”), you’ll see an option to set up continuous deployment: If you’ve already got a basic or standard web hosting plan with Azure then it’s free as you can load those guys up with as many sites as the service can bear. Here’s what I’ve done:įirstly, you get yourself a website. I needed something a bit more reliable though so I decided to tackle it by using Azure to publish the Dropbox content to a website which also means I can do a few other neat things too. They obviously don’t want the service hosting volumes of data that are served as if it was a website and I get that.
In fact this is exactly what I did last week – just as I’d done many times before – and then this started happening:Īdmittedly, I’ve hit this before too and it happens once you start pumping too much content out to the public via Dropbox. I normally put them in Dropbox, “Share Dropbox Link” then shorten it with my custom troy.hn short URL so they can read it from the screen in a meeting room and point them there. They’re not sensitive files, they’re things like exercises I might be running in workshops which I want people to download from a common location. I regularly share files with people that I want them to grab over HTTP from a location without any auth or other hurdles.
0 kommentar(er)
