Local Portal Light-Router

We now have some users who want to work on the light-portal to add more services and customize the UI to meet their requirements. In this tutorial, we are going to explore how to get the light-portal services started and exposed from light-router. With all the services available locally, we are going to demo how to use the proxy in React SPA to build UI with the hot reloader. In addition, we are going to show how to build and deploy the developed SPA to the router instance so that CORS can be avoided and maximize the performance.

This tutorial helps users to learn how to set up production like environment locally and how each component interact with each other to form an ecosystem. It provides an option for you to deploy these open source services on the cloud if you want to leverage them for your organization.

Start Portal

Deploy Portal View

To be written Read More »

OAuth2 Console

In the previous step, we have started the light-router instance for the local portal. It listens 443 for the host lightapi.net In this step, we are going to explore the lightapi.net UI implementation with a focus on the light-oauth2 view. For development, we are going to use a proxy to access APIs through light-router. The light-portal view can be accessed from light-portal/view folder. https://github.com/networknt/light-portal/tree/master/view proxy In the src folder, there is a setupProxy. Read More »

Portal View

In the previous step, we have started the light-router instance for the local portal. It listens to 443 for the host lightapi.net In this step, we are going to explore the lightapi.net UI implementation with a focus on the light-oauth2 view. For development, we are going to use a proxy to access APIs through light-router. The light-portal view can be accessed from light-portal/view folder. https://github.com/networknt/light-portal/tree/master/view proxy In the src folder, there is a setupProxy. Read More »

Start Local Light Router

In the previous step, we have started the light-oauth2 services locally. Now let’s start the light-router instance to be responsible for service discovery and to serve the resources later. For development, we are going to use the proxy from the create-react-app to connect to the light-router for all API accesses. Once the development is done, the SPA application will be built and copied to a folder named lightapi which match the domain lightapi. Read More »

Light OAuth 2.0 Services

In the previous step, we have started the consul server locally, now let’s start the light-oauth2 services as they are part of the portal. We will start more services later on, but here we use the light-oauth2 services to demo the process. We cannot use the docker-compose-oauth2-mysql.yml in light-docker as the configuration there is not using the consul registry. In order to use the consul registry and discovery, all services should be bound to the host network instead of the docker network. Read More »

Start Consul

In the previous step, we have the environment parepared. In this step, we are going to start the consul server for other subsequent services to register and discover services. All portal services will be registered to the Consul cluster on the official test/prod environment. To make sure that the local dev environment works the same. We are going to start the consul server locally with a docker-compose in the light-docker repository. Read More »

Prepare Environment

Before starting portal services locally, we need to make sure that Docker is installed. This tutorial is based on Ubuntu Linux, and I am sure that Mac OS should work the same. However, I am not sure that it will work on Windows. It would be great if someone can help to test it on the Windows environment. Check out We have docker-compose and config files checked into some repositories on the GitHub. Read More »