Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Browse files

Update README.md

Switching to master specifically for Travis badge
  • Loading branch information...
commit 036fb40051ec761e87c3facbdce1b30ed734f129 1 parent 837a6a0
@rickychilcott rickychilcott authored
Showing with 1 addition and 1 deletion.
  1. +1 −1  README.md
View
2  README.md
@@ -1,4 +1,4 @@
-[![Build Status](https://travis-ci.org/jnraine/munkiserver.png)](https://travis-ci.org/jnraine/munkiserver) [![Coverage Status](https://coveralls.io/repos/jnraine/munkiserver/badge.png)](https://coveralls.io/r/jnraine/munkiserver)
+[![Build Status](https://travis-ci.org/jnraine/munkiserver.png?branch=master)](https://travis-ci.org/jnraine/munkiserver) [![Coverage Status](https://coveralls.io/repos/jnraine/munkiserver/badge.png)](https://coveralls.io/r/jnraine/munkiserver)
Munkiserver is a Ruby on Rails web application for managing your munki clients. Clients are in a 1-1 relationship with the server (i.e. each client has their own manifest), making it easy to specify one off installs. However, you can still group clients together using computer groups and apply software bundles to them, thus achieving the same level of functionality as regular manifests in vanilla munki. All configurations (ex: pkginfo, manifests, bundles, etc…) are stored in a backend relationsl database; there is no flat repo. This adds some complexity however, all management is done through the web application:
Please sign in to comment.
Something went wrong with that request. Please try again.