Installation Kong Dashboard (II)

On the git Kong's rich party tools can be seen, this is also the choice of the management UI above a admin ui project.

Here is a list of third-party tools maintained by the community:
Ansible role for Kong on Ubuntu
• Biplane: declarative configuration in Crystal
• Bonobo: key management (with Mashery migration scripts)
• Chef cookbook
• Django Kong Admin: Admin UI in Python
• Jungle: Admin UI in JavaScript
• Kong Dashboard: Admin UI in JavaScript
• Kong for CanopyCloud
• Kong image waiting for Cassandra
• Kong image for Tutum
• Kong-UI: Admin UI in JavaScript
• Konga: CLI Admin tool in JavaScript
• Kongfig: Declarative configuration in JavaScript
• Kongfig on Puppet Forge
• Puppet recipe
• Python-Kong: Admin client library for Python
• .NET-Kong: Admin client library for .NET

First, install Dashboard

Installation Environment : centos 6.7
overall preparations to use the source code installation as an example:

  • Use management UI kong-dashboard based Node.js, it is necessary to install NodeJS;

  • Due to the use of resources and may occasionally github resources in the wall, it is recommended to use Taobao npm;

  • At the same time it will be used to bower;

  • npm install process takes c ++ 11 (due to my environment gcc versions earlier than 4.8 does not support c ++ 11, you need to upgrade to gcc version 4.8 or 4.8 above)

  • git clone down the folder permissions;

  • If you use the root user to install, you need to modify. FIG follows: Here Insert Picture DescriptionAfter the completion of preparations 7, it can be installed in accordance with the git steps of:

  • Pull repository

    git clone https://github.com/PGBI/kong-dashboard.git
     
    sudo chmod -R 777 kong-dashboard (该步非必须,需要根据实际情况进行文件夹读写权限设置)
     
    cd kong-dashboard
    
  • Build Kong Dashboard

    sudo npm install --unsafe-perm --registry=https://registry.npm.taobao.org
    
  • Start Kong Dashboard

    npm start
    
  • To start Kong Dashboard on a custom port

    npm start -- -p [port]
    

After a successful start, visit http: // localhost: 8080 Open Dashboard.

Second, the use Admin UI

Following is a brief mention only some caveats, the specific use and meaning of the content on the UI display kong refer to the doc.

  1. Configuration Notes address (kong management address, the default is http: // kong server machine or domain binding: 8001
    behind Do not pay more "/" as shown below or click on the tips not found api API like there will be, of course, have
    to ensure that kong server normal operation.  
    Here Insert Picture Description

  2. When adding the new API and the API used, if necessary to note the address that points using api, i.e. you need to check the strip-request path; If you use the tape head address request, need to take X-Host-Override in the head post.demo (ie request host)
    Here Insert Picture Description
    need to be used with caution, address requests for http: // kong server machine or binding domain: 8000 (api below shows the way in the url with the request)
    Here Insert Picture Description

  3. Examples of the use of plug-ins, using the key-auth plugin:

  1. We need to create plug-auth key basis in api
  2. Set the plug-keyname (Note that this keyname will be used later in the url)  Here Insert Picture Description   
    When enabled plug-in, if the latter does not have the right keyname in the address bar or header in the following prompt:       
    Here Insert Picture Description
    If you key in the address bar behind the header or incorrect will be the following prompt
     Here Insert Picture Description
  3. New customer and to set its contents may be considered the key to a value above (corresponding to the above-described where used temporarily auth key) keyname corresponding to the actual access for the use of
    Here Insert Picture Description
  4. Use (requested address is http: // domain or binding kong server machine: 8000)
     Here Insert Picture Descriptionor FIG header as follows:
     Here Insert Picture Description

Guess you like

Origin blog.csdn.net/sa19861211/article/details/92223359