This is great, Cory (and Ben)! Out of curiosity, what were the trickiest parts of writing the plugin? Also, what aspects/components of juju's architecture helped and hindered you?
-eric On Fri, Apr 24, 2015 at 6:34 AM, Cory Johns <cory.jo...@canonical.com> wrote: > Last week, while in Nuremberg, Ben and I were able to create a new > plugin to enable a much better charm development workflow. > > Once the Juju Plugins bundle (https://github.com/juju/plugins) is > installed, you can now run `juju sync-watch <unit>` to enable local > editing of a remote charm. This works using inotify to watch for > changes in the local copy of the charm and automatically sync those > changes up to the deployed unit. If the unit is in an error state, it > will also automatically retry the failed hook, so that you can do > fast, seamless iteration on a charm. > > This plugin works with any provider and any editor. > > -- > Juju mailing list > Juju@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
