tag:blogger.com,1999:blog-9238405.post4862310228319623015..comments2026-04-17T02:13:19.234-07:00Grig Gheorghiuhttp://www.blogger.com/profile/17863511617654196370noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-9238405.post-27896710545554792812010-10-27T22:51:21.260-07:002010-10-27T22:51:21.260-07:00Sorry for reporting this via a comment, but both ATOM and RSS feeds tell me this in Firefox (I replaced angle brackets with round brackets): XML Parsing Error: undefined entity<br />Location: jar:file:///usr/lib/firefox-3.6.11/chrome/browser.jar!/content/browser/feeds/subscribe.xhtml<br />Line Number 22, Column 12: (title)&amp;feedPage.title;(/title)<br />-----------^Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-9238405.post-66070060043753705882010-10-15T02:49:38.794-07:002010-10-15T02:49:38.794-07:00Hi!<br /><br />I would like to add something here. Actually, nobody but potential contributors should care about whether Overmind is written in Python. It could use Ruby on Rails and it would be the same. You use a UI, or you use a REST API.<br /><br />The motivation was that no project exists that is a provider independent front-end and integrates configuration management and monitoring. We hope to get there.<br /><br />What Python devops <b>do care</b> about is that Chef is ruby.Because they actually have to use ruby cookbooks and develop new deployments in ruby.<br /><br />While it is not guaranteed, I hope to be able to design a plugin architecture with Chef-solo, Puppetd, kokki and fabric plugins so that both Ruby and Python devs can be happy and use Overmind.<br /><br />Exactly the same way that we have integrated libcloud drivers as plugins, as well as allowed for anyone to include any custom provider as just another plugin.<br /><br />Have a nice day!<br />Miqueltobamihttps://www.blogger.com/profile/16388550213568324790noreply@blogger.com