Skip to content

Latest commit

 

History

History
117 lines (73 loc) · 2.47 KB

README.md

File metadata and controls

117 lines (73 loc) · 2.47 KB
Raw

Macwifibeat

Welcome to Macwifibeat.

Ensure that this folder is at the following location: ${GOPATH}/src/github.com/bozdag/macwifibeat

Getting Started with Macwifibeat

Requirements

Init Project

To get running with Macwifibeat and also install the dependencies, run the following command:

make setup

It will create a clean git history for each major step. Note that you can always rewrite the history if you wish before pushing your changes.

To push Macwifibeat in the git repository, run the following commands:

git remote set-url origin https://github.com/bozdag/macwifibeat
git push origin master

For further development, check out the beat developer guide.

Build

To build the binary for Macwifibeat run the command below. This will generate a binary in the same directory with the name macwifibeat.

make

Run

To run Macwifibeat with debugging output enabled, run:

./macwifibeat -c macwifibeat.yml -e -d "*"

Test

To test Macwifibeat, run the following command:

make testsuite

alternatively:

make unit-tests
make system-tests
make integration-tests
make coverage-report

The test coverage is reported in the folder ./build/coverage/

Update

Each beat has a template for the mapping in elasticsearch and a documentation for the fields which is automatically generated based on fields.yml by running the following command.

make update

Cleanup

To clean Macwifibeat source code, run the following commands:

make fmt
make simplify

To clean up the build directory and generated artifacts, run:

make clean

Clone

To clone Macwifibeat from the git repository, run the following commands:

mkdir -p ${GOPATH}/src/github.com/bozdag/macwifibeat
git clone https://github.com/bozdag/macwifibeat ${GOPATH}/src/github.com/bozdag/macwifibeat

For further development, check out the beat developer guide.

Packaging

The beat frameworks provides tools to crosscompile and package your beat for different platforms. This requires docker and vendoring as described above. To build packages of your beat, run the following command:

make release

This will fetch and create all images required for the build process. The whole process to finish can take several minutes.