Smart group my droplets

[nofxx]

Planning to make droplets list more clear, currently (if #77 gets merged) , supposing 2 projects, multiple servers you'll end up with something like:

ON   foo-db1              16.213.17.111    @ New York 2      #123456
ON   foo-web1             16.213.17.111    @ New York 2      #123456
ON   bar-db1              16.213.17.111    @ New York 2      #123456
ON   bar-web1             16.213.17.111    @ New York 2      #123456
....

I propose a split and group with '-' hifens:

bar
    ON   db1.foo.com               16.213.17.111    @ New York 2      #123456
    ON   web1.foo.com              16.213.17.111    @  New York 2      #123456
foo
    ON   db1.foo.com               16.213.17.111    @ New York 2      #123456
    ON   web1.foo.com              16.213.17.111    @  New York 2      #123456
    ....

Kinda like linode groups. We could also do actions on groups, like god (monit). You may not provide any hifen, so the listing will be the same. Also, maybe a option to don't group. Any ideas?

[pearkes]

Yea, this is a cool idea. I see the use case (I name my machines the same way per project).

I think we'd want to make this opt-in, though, perhaps through the ~/.tugboat configuration as well as a flag on tugboat droplets.

What the behavior be if I didn't have a leading slash on a droplet name? Would it just append it to the the bottom of the list with no group or indentation?

[tjcran]

Tagging droplets is now possible through the DigitalOcean API, so integrating into Tugboat should be straightforward: https://developers.digitalocean.com/documentation/v2/#tags

[petems]

That's pretty cool, should be fairly easy to implement as you say. I might be able to get a basic implementation done on Sunday :)