<story><title>Show HN: Config.ly – Never hardcode your data again</title><url>https://www.config.ly</url></story><parent_chain></parent_chain><comment><author>munro</author><text>I don&amp;#x27;t understand why people use config servers like this, instead of keeping it in version control.  Keeping it in the repository allows me audit changes of everything.  If you move it to an external service, you lose that.  And even if the external service has an audit trail, now you have two sources of version control.  My assumption why people would do this is because 1) they&amp;#x27;re told that&amp;#x27;s how it should be done 2) they have a slow deployment processes, where it takes too long to get the change merged &amp;amp; deployed.  Anyway, I&amp;#x27;ve very happily never used a config service, and I still remain unconvinced.  :)</text></comment>
<story><title>Show HN: Config.ly – Never hardcode your data again</title><url>https://www.config.ly</url></story><parent_chain></parent_chain><comment><author>jeremyis</author><text>I’m Jeremy, cofounder of Config.ly. It’s like a CMS for your static variables &amp;#x2F; copy &amp;#x2F; constants so you can easily update them from a web UI instead of deploying code.&lt;p&gt;We’re software engineers and saw that the source of many bugs, incidents and time-sinks stem from hard-coding data. For example - waiting a day or longer for an iOS app store approval of a copy change, waiting hours on an internal CI&amp;#x2F;deployment process to bump a timeout during a traffic spike incident, or having the same dollar-cost value diverge while hard-coded on iOS, Android and web clients.&lt;p&gt;In an ideal world, data would be completely separate from code. Databases can do this but often aren’t used that way for good reasons (they can be cumbersome to wire-up, there are scale concerns about adding extra load to your DB, it’s risky to touch a production database, etc). So we built Config.ly.&lt;p&gt;It has a simple web interface to define Strings, Numbers, Booleans and JSON objects and arrays. We think it’s so simple that even non-technical folks can update basic Config data like copy and colors (so you can focus on code!). We have client libraries (in four techs and growing!) that fetch these values from the server and intelligently handle optimizations like caching.&lt;p&gt;It’s free to use (with genorous size and bandwidth caps) and getting started from sign-up to fetching values in your client should take &amp;lt; 5 minutes.&lt;p&gt;And we’d love to hear what you think!</text></comment>