Oh, this wasn't meant to sound so sarcy! I was working through them one by
one and commenting as I went but I forgot to fix this comment. It does
indeed do what you said when I ran and tested that command :) this was just
a place holder for me to expand the "something"
On 5 Jul 2013 20:00, "Ian McEwen" <notifications@github.com> wrote:

> In upstream_manager.py:
>
> > -    actions[action](config, cluster, args[2:], options, parser)
> > +    parser = argparse.ArgumentParser()
> > +    parser.add_argument('-c', '--config', type=config,
> > +                        help='Path to the abstract YAML configuration',
> > +                        default='config.yaml')
> > +    parser.add_argument('-o', '--output', help='path to generate nginx configuration')
> > +    parser.add_argument('cluster')
> > +
> > +    subparsers = parser.add_subparsers()
> > +
> > +    # The 'generate' command generates nginx configuration files
> > +    generate = subparsers.add_parser('generate',
> > +                                     help='generate a concrete nginx configuration from the abstract cluster description')
> > +    generate.set_defaults(run=generate_action)
> > +
> > +    # The 'rotate' command does... something
>
> The rotate command is what we use for musicbrainz-server deployments. The
> first time you call it, it disables one server and prints it out, which
> fabric should capture and deploy to that server. Then, when called again,
> it brings that one back in and takes out the next, printing out the IP;
> then you can deploy to that, and so forth until it's done all
> non-disabled/non-'down' servers, at which point it'll print out 'Done' and
> you know you're finished.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/ianmcorvidae/nginx-upstream-manager/pull/2/files#r5048309>
> .
>