README.md in stove-3.2.3 vs README.md in stove-3.2.4
- old
+ new
@@ -1,16 +1,12 @@
Stove
=====
-[![Gem Version](http://img.shields.io/gem/v/stove.svg)][gem]
-[![Build Status](http://img.shields.io/travis/sethvargo/stove.svg)][travis]
-[![Dependency Status](http://img.shields.io/gemnasium/sethvargo/stove.svg)][gemnasium]
-[![Code Climate](http://img.shields.io/codeclimate/github/sethvargo/stove.svg)][codeclimate]
+[![Gem Version](http://img.shields.io/gem/v/stove.svg?style=flat-square)][gem]
+[![Build Status](http://img.shields.io/travis/sethvargo/stove.svg?style=flat-square)][travis]
[gem]: https://rubygems.org/gems/stove
[travis]: http://travis-ci.org/sethvargo/stove
-[gemnasium]: https://gemnasium.com/sethvargo/stove
-[codeclimate]: https://codeclimate.com/github/sethvargo/stove
A utility for releasing and managing Chef Cookbooks. It will:
- Tag and push a new release to git
- Upload the cookbook to a cookbook share (such as Supermarket)
@@ -38,17 +34,22 @@
```bash
$ stove login --username sethvargo --key ~/.chef/sethvargo.pem
```
-These values will be saved in Stove's configuration file and persisted across your workstation.
+These values will be saved in Stove's configuration file (`~/.stove`) and persisted across your workstation.
The default publishing endpoint is the [Chef Supermarket](https://supermarket.getchef.com), but this is configurable. If you want to publish to an internal community site, you can specify the `--endpoint` value:
```bash
$ stove --endpoint https://internal-cookbook-store.example.com
```
+or for a private supermarket using the [supermarket](https://supermarket.getchef.com/cookbooks/supermarket) cookbook:
+
+```bash
+$ stove --endpoint https://internal-cookbook-store.example.com/api/v1
+```
Usage
-----
There are two ways to use Stove. You can either use the `stove` command directly or use the embedded rake task.