Skip to content

Commit

Permalink
Fixup readme
Browse files Browse the repository at this point in the history
  • Loading branch information
basepi committed Jan 5, 2017
1 parent efea897 commit 1e12d64
Showing 1 changed file with 11 additions and 14 deletions.
25 changes: 11 additions & 14 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,11 +1,13 @@
# Hubble
The infamous HubbleStack written in Python to run autonomously (independent of SaltStack).

An alternate version of Hubblestack which can be run without an existing
SaltStack infrastructure.

# Installation/testing

```bash
git clone git@github.com:dmcteer/hubble hubblev2
cd hubblev2
git clone git@github.com:hubblestack/hubble
cd hubble
python setup.py clean && python setup.py install
hubble
```
Expand All @@ -23,22 +25,15 @@ python-pygit2 to get gitfs working:

```
gitfs_remotes:
- https://github.com/hubblestack/Nova.git:
- base: v2016.10.2
- https://github.com/hubblestack/Nebula.git:
- base: v2016.10.2
- https://github.com/hubblestack/Pulsar.git:
- base: v2016.10.3
- https://github.com/hubblestack/Quasar.git:
- base: v2016.10.4
- https://github.com/hubblestack/hubble.git:
fileserver_backend:
- root
- git
```

## Single invocation

Hubble v2 now supports one-off invocations of specific functions:
Hubble supports one-off invocations of specific functions:

```
[root@host1 hubble-v2]# hubble nova.audit cis.centos-7-level-1-scored-v2-1-0 tags=CIS-3.\*
Expand Down Expand Up @@ -67,8 +62,10 @@ Hubble v2 now supports one-off invocations of specific functions:

## Scheduler

Hubble v2 now supports scheduled jobs. See the docstring for `schedule` for
more information, but it follows the basic structure of salt scheduled jobs:
Hubble supports scheduled jobs. See the docstring for `schedule` for
more information, but it follows the basic structure of salt scheduled jobs.
The schedule config should be placed in `/etc/hubble/hubble` along with any
other hubble config:

```
schedule:
Expand Down

0 comments on commit 1e12d64

Please sign in to comment.