Public | Automated Build

Last pushed: 4 months ago
Short Description
container for use in building kibana plugins
Full Description

kibana-plugin-dev-env

a dev env for kibana plugins

Prereqs

  • docker
  • docker-compose is optional.

Usage

  1. make a custom entry script such as saved as ./dev-entry.sh
    #!/bin/bash
    npm install
    npm run build
    npm start -- --elasticsearch.url "${ELASTICSEARCH_URL}" --no-ssl --server.host "${SERVER_NAME}"
    

if using docker-compose

  1. edit docker-compose.yml in your plugin folder.
    version: '2'
    services:
    kibana:
     container_name: kibana-plugin-dev
     image: docker-remote.registry.kroger.com/danfrohlich/kibana-plugin-dev-env:v5.4.1
     entrypoint: /project/plugin_folder/dev-entry.sh
     environment:
       ELASTICSEARCH_URL: http://[your-es-host-here]:9200
       SERVER_NAME: 0.0.0.0
     volumes:
       - .:/project/plugin_folder
     ports:
       - "5601:5601"
     working_dir: /project/plugin_folder
    
  2. docker-compose up

docker (not using docker-compose)

  1. run the container.
    docker run -d \
    --name kibana-plugin-dev \
    --entrypoint /project/plugin_folder/dev-entry.sh \
    -v .:/project/plugin_folder \
    -p 5601:5601 \
    -e "ELASTICSEARCH_URL=http://[your-es-host-here]:9200" \
    -w /project/plugin_folder \
    -e "SERVER_NAME=0.0.0.0" \
    docker-remote.registry.kroger.com/danfrohlich/kibana-plugin-dev-env:v5.4.1
    

to run tets cases...

  1. enter running container
    docker exec -it kibana-plugin-dev bash
    
  2. execute helper testing tasks
    plugin-helpers test:server
    
    plugin-helpers test:browser
    

RELEASE NOTES

  • updated to kibana v5.5.1
Docker Pull Command
Owner
danfrohlich