Open device management
Find a file
2016-08-09 19:17:07 -07:00
app Improve error handling throughout backend (#50) 2016-08-09 19:04:28 -07:00
config Fix certificate path in development config (#55) 2016-08-09 16:18:03 -07:00
errors Improve error handling throughout backend (#50) 2016-08-09 19:04:28 -07:00
Godeps Improve error handling throughout backend (#50) 2016-08-09 19:04:28 -07:00
sessions Improve error handling throughout backend (#50) 2016-08-09 19:04:28 -07:00
tools Updating README and documentation to reflect local building and testing (#58) 2016-08-09 19:17:07 -07:00
.gitignore Improve error handling throughout backend (#50) 2016-08-09 19:04:28 -07:00
circle.yml Attempt to clean the codebase (#53) 2016-08-09 10:24:29 -07:00
docker-compose.yml Updating README and documentation to reflect local building and testing (#58) 2016-08-09 19:17:07 -07:00
kolide.go Fix certificate path in development config (#55) 2016-08-09 16:18:03 -07:00
README.md Updating README and documentation to reflect local building and testing (#58) 2016-08-09 19:17:07 -07:00

Kolide CircleCI

Building

To build the code, run the following from the root of the repository:

# On Linux, OS X, etc:
go build -o kolide

# On Windows:
go build -o kolide.exe

Testing

To run the application's tests, run the following from the root of the repository:

go vet ./... && go test -v ./...

Development Environment

To set up a canonical development environment via docker, run the following from the root of the repository:

docker-compose up

This requires that you have docker installed. At this point in time, automatic configuration tools are not included with this project.

Once you docker-compose up and are running the databases, you can build the code and run the following command to create the database tables:

kolide prepare-db

Now you are prepared to run a Kolide development environment. Run the following:

kolide serve

You may have to edit the example configuration file to reflect localhost if you're using Docker via a native docker engine or the output of docker-machine ip if you're using Docker via docker-toolbox.

If you'd like to shut down the virtual infrastructure created by docker, run the following from the root of the repository:

docker-compose down