Application Scenarios of Pylon CLI —— A Client Tool that Controls the Dev Environment Locally

As a front-end engineer, Node is an essential development tool for java. Currently, most projects I am in charge of are based on Node 12.

At this time, I thought of TeamCode, a cloud collaborative development platform that I used before. It provides some high-performance and lightweight tools. I just thought of their official updates on Facebook which notifies me that the product Pylon has a new tool called Pylon CLI, which seems has features that could satisfy my demands.

I went to its official website and started to check the documents of Pylon CLI: It is a client tool that controls the Pylon development environment locally. You can build a development environment locally through the Git repository address and manage all locally created development environments.

Then I started to download and install the CLI according to the guidance, and created the latest version of Node 16.

Download Node 16;

And created gatsby-starter-blog successfully.

Open the gatsby-starter-blog with VSCode.

In this way, I ran and started gatsby-starter-blog on your computer without worrying about environmental conflicts or coordination issues.

For most developers, the local computing power is sufficient, and there is no additional cost to set up a cloud-based development environment. However, there will be some adaptation and compatibility problems in the local development environment. The most obvious issue is that there is no environment isolation, and the versions of dependencies required by different projects are inconsistent, resulting in the failure to run projects. Pylon CLI is designed to solve these problems. It can build and manage multiple local development environments quickly. Different sub-development environments are isolated from each other, meeting the requirements of the operating environment for different projects, that's the reason I chose it.