When you run your Orchard Core site on DotNest, there are some limitations that you need to keep in mind. These are inherent to the multi-tenant nature of DotNest: We can provide you with super-simple, fast, convenient Orchard Core hosting because when you set up your site, you'll get a slot in the same app as everyone else. We always want to push boundaries though. So now, we introduce full theming for your DotNest sites with Media Theme! The Media Theme concept is about storing a kind-of-theme in the Media Library (but still safely, so nobody can see your code). What matters more for you though, is that with this, you can now create proper Orchard Core themes in your favorite IDE with Liquid templates and all the client-side web technologies. And when you're finished, you can deploy it from the command line or a CI build automatically to your DotNest site! Here we also have a quick demo of how this works. Also, check out the DotNest Core SDK: You have all the instructions there to have a local development environment ready, to work on your site locally as you'd on any Orchard Core app, and then to deploy it to DotNest. We're also working on a couple of case studies since there are some sites we're already created with this new approach. Would you like to run your Orchard Core site on DotNest? Sign up for the beta! (We'll soon be out of beta, promise!)

Update time! In this round we fixed some bugs that arose recently, among others one with Media Theme deployment that caused the deployment hook not to work correctly in all circumstances. Also we made some changes to the subsystem that is responsible for running maintenances tasks. This means that we can now make upgrades more safely, keeping your sites up-to-date all the time without you even noticing.

Today we reached the point where we fixed every bug that came up during the few first days of DotNest. This doesn't mean it's perfect but currently we don't know about any important errors at least. Here are the two main issues we fixed: Issues when Jobs Queue when using together with Media Theme Deployment Redirects now work correctly when you're using custom domains. (Because you can point your domain to your DotNest site completely free!) There were some other, smaller fixes too. By the way, did you notice how fast the sites running on DotNest are?

Only a few days after announcing DotNest (see the recording about it), we've released the first set of updates ('cause that's how we roll on Saturday evenings). Let's see what changed! MediaTheme deployment works (again, but you didn't see that before). SSL for tenants works on port 8443, work is still in progress to make it work on port 443. You can suspend your tenants if you want to disable them temporarily and then you can re-awaken them. It is also possible to delete a tenant - be aware that this action is immediate and irreversible. A little technical detail (may be interesting for the fellow devs): Orchard.Azure is upgraded to the latest 1.x source, which gives us much more flexibility regarding the configuration of DotNest. More importantly, the storage (Media and Indexing) performs faster and more efficiently with this upgrade. Happy Orchardin'! - The guys @ Lombiq