empayre/fleet
14
0
Fork 0
mirror of https://github.com/empayre/fleet.git synced 2024-11-06 08:55:24 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

rename old references to the binary (#1638)

Browse Source
This commit is contained in:
Victor Vrantchan 2017-11-18 19:58:19 -05:00 committed by GitHub
parent 11707132bd
commit b2771b80c0
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
4 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/application/working-with-osquery-logs.md
View File

@ -1,7 +1,7 @@
Working With Osquery Logs Working With Osquery Logs
========================= =========================
The `kolide` binary accepts two flags: The `fleet` binary accepts two flags:
- `--osquery_result_log_file`: Path for osqueryd result logs (default: `/tmp/osquery_result`) - `--osquery_result_log_file`: Path for osqueryd result logs (default: `/tmp/osquery_result`)
- `--osquery_status_log_file`: Path for osqueryd status logs (default `/tmp/osquery_status`) - `--osquery_status_log_file`: Path for osqueryd status logs (default `/tmp/osquery_status`)

2
docs/development/database-migrations.md
View File

@ -19,7 +19,7 @@ Find the file you created in the migrations directory and edit it. You can then
``` bash ``` bash
make build make build
build/kolide prepare db build/fleet prepare db
``` ```
## Populating the database with default data ## Populating the database with default data

6
docs/development/development-infrastructure.md
View File

@ -24,7 +24,7 @@ docker-compose down
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: 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 fleet prepare db
``` ```
## Running Fleet using Docker development infrastructure ## Running Fleet using Docker development infrastructure
@ -32,9 +32,9 @@ kolide prepare db
To start the Fleet server backed by the Docker development infrasturcture, run the Fleet binary as follows: To start the Fleet server backed by the Docker development infrasturcture, run the Fleet binary as follows:
``` ```
kolide serve fleet serve
``` ```
By default, Fleet will try to connect to servers running on default ports on localhost. By default, Fleet will try to connect to servers running on default ports on localhost.
If you're using Docker via [Docker Toolbox](https://www.docker.com/products/docker-toolbox), you may have to modify the default values use the output of `docker-machine ip` instead of `localhost`. There is an example configuration file included in this repository to make this process easier for you. Use the `--config` flag of the Fleet binary to specify the path to your config. See `kolide --help` for more options. If you're using Docker via [Docker Toolbox](https://www.docker.com/products/docker-toolbox), you may have to modify the default values use the output of `docker-machine ip` instead of `localhost`. There is an example configuration file included in this repository to make this process easier for you. Use the `--config` flag of the Fleet binary to specify the path to your config. See `fleet --help` for more options.

2
docs/development/testing.md
View File

@ -105,4 +105,4 @@ mail:
address: localhost:1025 address: localhost:1025
``` ```
`localhost:1025` is the default configuration. You can use `kolide config_dump` to see the values which Fleet is using given your configuration. `localhost:1025` is the default configuration. You can use `fleet config_dump` to see the values which Fleet is using given your configuration.