Closed peterldowns closed 11 years ago
Hey @peterldowns
The client library has all you need to work with switches. It has all the functionality to create switches, add conditions to them and use them on your application code. One thing it doesn't have is a web interface, but I'm currently working on a chimera-web
package that will provide a web interface to administer switches like you do today with gargoyle.
You can certainly build and use switches in python today if you want - which may be all that you need for your use case. The backing data store for chimera is modeldict, which syncs instances of the dict with some sort of persistant storage. That means that you can update your switches via the CLI and the changes will be reflected (after cache expires) on all modeldict instances, including ones running your production app.
We (Disqus) heavily use gargoyle
right now and will have some tools available to migrate from gargoyle
to chimera
. The underlying data structure between the two are not similar so you may have to manually migrate some switches, but I'm gonna try to minimize that.
My suggestion for you now is to use gargoyle
and migrate to chimera
(if needed) once it's available. Chimera hasn't made it into production for us yet and the chimera-web
package is still a week or two away, so it will be a little bit before we'll have confidence in it. And, as I said earlier, the migration should be relatively painless.
I'm gonna close this since this isn't really an issue, but feel free to add some more comments or questions.
Hello, I just recently started using
gargoyle
, but it looks like it's being deprecated in favor ofchimera
. This seems to be the client library, but do you know when the underlyingchimera
library will exist? I'd hate to start using Gargoyle and have to switch to Chimera a month from now.Peter