Geeks With Blogs

News This is the *old* blog. The new one is at blog.sixeyed.com
Elton Stoneman
This is the *old* blog. The new one is at blog.sixeyed.com
APIs
Using CMS for App Configuration - Part 3, Consume Your Config
After Part 1 and Part 2, we now have an app config server with a nice UI and a publishing workflow for changes. In our app, we can get the current config settings with an HTTP client reading from the URL for the config document: http://config.mydomain.com/... And we’ll get a response like this: { "connectionStrings": { "redis": "connection;string;goes;her... "sqlServer": "and;for;sql;" }, "caching": { "lifespan": "PT10M", "maximumSize": 300 }, "appSettings": { "termsAndConditionsUrl": "http://static.xyz.com/tand... ......

Posted On Friday, June 27, 2014 12:16 PM

Using CMS for App Configuration - Part 2, Publish Your Config
Following on from Part 1 – Deploying Umbraco, we have a nice new installation of Umbraco, hosted in an Azure Website and using SQL Azure for storage. In this post, we’re going to define some configuration settings for an application, capture the settings for one environment, and publish them as JSON – all without leaving Umbraco. Define the Document Type In Umbraco, content templates are called Document Types, and they’re set up in the Settings section from the left hand nav. We can host the config ......

Posted On Friday, June 13, 2014 7:47 PM

Using CMS for App Configuration - Part 1, Deploying Umbraco
Since my last post on using CMS for semi-static API content, How about a new platform for your next API… a CMS?, I’ve been using the idea for centralized app configuration, and this post is the first in a series that will walk through how to do that, step-by-step. The approach gives you a platform-independent, easily configurable way to specify your application configuration for different environments, with a built-in approval workflow, change auditing and the ability to easily rollback to previous ......

Posted On Wednesday, June 4, 2014 7:56 PM

How about a new platform for your next API… a CMS?
Say what? I’m seeing a type of API emerge which serves static or long-lived resources, which are mostly read-only and have a controlled process to update the data that gets served. Think of something like an app configuration API, where you want a central location for changeable settings. You could use this server side to store database connection strings and keep all your instances in sync, or it could be used client side to push changes out to all users (and potentially driving A/B or MVT testing). ......

Posted On Thursday, May 22, 2014 8:02 AM

Copyright © Elton Stoneman | Powered by: GeeksWithBlogs.net