Once your configuration files have been tuned to suit your environment, it's
time to cover the 2 scripts available to the user. These scripts are located in
$PATH and are important tools to understand:
This script writes your configuration files (
to their factory default state. This script is already run at install so
it's not necessary to run right now.
So why do I care about this generate_defaults.sh thing?
Great question! This very helpful when you begin editing your configs and get into a mess. It's a solution for when you need to restore the base configuration files back to their factory defaults.
Simply execute the script to get you out of config file purgatory:
It's important to note that this resets configuration files and not any data.
Now it's finally time to deploy this thing. This is done by running the deployment script, which is kicked off by running:
Once the deployment is completed with the components you chose, you'll be congratulated with a success banner. Congratulations!
Initial Kibana Access¶
We strive to do the little things right, so rather than having Kibana available to everyone in the free world, it's sitting behind a reverse proxy and secured by a passphrase.
The credentials are written to the home directory of the user that runs the
deploy script. Most of the time, this will be the administrative user
created at installation e.g.
To get into Kibana:
- copy the passphrase in
- point your browser to Kibana:
https://[hostname](if you have DNS set up)
- enter user and password