Loading repository data…
Loading repository data…
bovino / repository
Fork from Kong Template... but with Docker / Docker compose to make your life a little easier by not having to install Kong (and Konga) locally to test or start developing your own custom plugins in Lua or in JavaScript. This project have 2 custom plugins (one in Lua and the other in JS using kong-js-pdk) already configured and running in one route and is also using the newer 2.4.x kong release.
A transparent discovery signal based on current public GitHub metadata.
This score does not audit code, security, maintainers, documentation quality, or suitability. Verify the repository and its current documentation before adoption.
docker-compose up -ddocker-compose restart (or down and up) and make the requests again to see your changes appliedAfter importing the collection you should see something like this:
This repository contains a simple Kong plugin template to get you up and running quickly for developing your own plugins.
In fact, this "template" has two custom plugin samples both installed and activated, one in Lua and the other using JavaScript, running in the new kong-js-pdf (please check here https://www.npmjs.com/package/kong-pdk and also here https://github.com/Kong/kong-js-pdk). The template is also configured to use the new 3.3.1 release of Kong (using 2.8.1-alpine docker image).
There are two JS plugins here:
There is also a Lua plugin contained in this template that was designed to work with
kong-pongo.
This project is a fork of the original kong plugin template project (https://github.com/Kong/kong-plugin) with the addition of Docker setup for Kong itself (with two custom JS plugins already activated in one service and a third one activated only in a route) and kong-js-pdk (needed to run the JavaScript plugin samples).
To start the containers:
docker-compose up or docker-compose up --build or docker-compose up -d
You need the following ports available:
Now you can make a request to a route and see one of the the activated plugin in action. To perform this, just make a GET request to (http://localhost:8000/v1/my-plugin-data).
You can also make POST requests to the URL http://localhost:8000/v3/my-plugin-data to see a JS plugin performing some body validation and printing.
To confirm the plugin is activated and working, look the response headers or check the logs being printed in the terminal (running docker-compose with -d flag).
To stop the containers:
docker-compose down