I was investigating taking an existing umbraco 6.1.6 site and re-architecting it, creating a separate (databaseless) front-end and an umbraco back-end; the front end would be a standard azure cloud service and the umbraco back-end could be a azure web site. My question is about the umbraco xml cache file, Umbraco.Config?
How do I make the backend's umbraco.config file accessible by the public front-end ? The 2 are completely de-coupled.
To me it sounds like you should explore the option to make use of Web API to expose your data using different API's and thereby not worrying about how to share the XML cache but serve data using the API's.
UPDATE: I am past halfway in the presentation but there's no mention of the umbraco.config xml cache file. Is that used at all by tombola platform?
I've seen the part about the cache and couchbase but that's not about the umbraco.config xml file is it?
umbraco servers all look after their own cache.
the cache in our presentation is an extra cache layer in case the umbraco servers go offline, our front end web servers would still work even with no umbraco servers
basically our web servers are "clients" and when you need content we call umbraco via its api endpoints (we built a custom library to handle this and cache the responses in between).
the "client" and server (umbraco) are disconnected, no need to interfere with umbraco's xml cache
Decoupling Umbraco from your front-end website
I was investigating taking an existing umbraco 6.1.6 site and re-architecting it, creating a separate (databaseless) front-end and an umbraco back-end; the front end would be a standard azure cloud service and the umbraco back-end could be a azure web site. My question is about the umbraco xml cache file, Umbraco.Config? How do I make the backend's umbraco.config file accessible by the public front-end ? The 2 are completely de-coupled.
Hi Charlie
To me it sounds like you should explore the option to make use of Web API to expose your data using different API's and thereby not worrying about how to share the XML cache but serve data using the API's.
If my memory is correct you should be able to make use of Web API in Umbraco 6 too - You can learn more about it here https://our.umbraco.com/documentation/Reference/Routing/WebApi/
I'm not sure but you might need to deal with CORS if taking this route, which you can read a bit more about here https://stackoverflow.com/questions/34748039/enable-cors-in-umbraco-6-web-api-2-instance - But I guess that depends on your setup.
Just my 2 cents - Hope they are useful :-)
/Jan
Just to toss a crazy idea into the mix, you could convert the XML to JSON with a few lines of code (because JSON is super easy to consume on the backend and frontend): https://www.newtonsoft.com/json/help/html/ConvertXmlToJson.htm
Then you'd need some way of passing that to the other server. You could go with Jan's suggestion of creating an API.
Another idea would be to transfer the JSON as a file to some central location both servers have access to (e.g., Azure blob storage).
sounds like you need umbraco's new headless solution or make your own like we did: https://codegarden18.com/sessions/headless-umbraco-cockroaches-and-aws-a-great-mix-for-our-players/
Phil- Thanks. I'll take a look!
Phil- Thanks. I'll take a look!
UPDATE: I am past halfway in the presentation but there's no mention of the umbraco.config xml cache file. Is that used at all by tombola platform? I've seen the part about the cache and couchbase but that's not about the umbraco.config xml file is it?
umbraco servers all look after their own cache. the cache in our presentation is an extra cache layer in case the umbraco servers go offline, our front end web servers would still work even with no umbraco servers
basically our web servers are "clients" and when you need content we call umbraco via its api endpoints (we built a custom library to handle this and cache the responses in between). the "client" and server (umbraco) are disconnected, no need to interfere with umbraco's xml cache
is working on a reply...