💻 Developing a Pluto Application Locally

npm install
pip install -r ./requirements.txt

After installing the dependencies, you can modify the app/main.py file according to your requirements to complete the application development. Of course, you can also directly deploy the example application to experience the use of Pluto.

When deploying, Pluto will package several functions included in the application into container images and upload them to the specified image repository. The container image name built by Pluto consists of: <registry>/<formatted_project_name>:<function_id>-<timestamp>.

Therefore, if you wish to upload to a public image repository, you need to create an image repository named after the project on platforms like Docker Hub, then configure the image repository address in the Pluto configuration file in the same manner. Note that to avoid illegal characters, we format the project name into a combination of lowercase letters and hyphens when uploading images. You can enter the project name below to get the formatted result and create the image repository accordingly:

Next, we fill in the image repository address into Pluto's configuration file. Open the .pluto/pluto.yml configuration file in the project directory, find the stack you created (default is dev), modify the configs field, and fill in the image repository address as follows:

...
stacks:
  - name: dev
    configs:
      kubernetes:registry: docker.io/your-username/
      kubernetes:platform: auto # or linux/amd64, linux/arm64
...

In the Kubernetes cluster, we can use the kubectl port-forward command to expose the service locally and then test whether the service is working properly with the curl command. You can use the following command to run kubectl port-forward in the background, or you can choose to open another terminal window to execute it:

nohup kubectl port-forward --namespace=ingress-nginx service/ingress-nginx-controller 8080:80 > /dev/null 2>&1 &

Then, we can test whether the service is working properly by executing the following two commands in sequence. hello-pluto-dev-plutolang-pluto-router-router.localdev.me is the access address output at the end of Pluto's deployment. If your Pluto application name is not hello-pluto, you need to replace it completely with the access address you obtained:

curl --resolve hello-pluto-dev-plutolang-pluto-router-router.localdev.me:8080:127.0.0.1 \
	http://hello-pluto-dev-plutolang-pluto-router-router.localdev.me:8080/hello
curl --resolve hello-pluto-dev-plutolang-pluto-router-router.localdev.me:8080:127.0.0.1 \
	http://hello-pluto-dev-plutolang-pluto-router-router.localdev.me:8080/store

If deployed successfully, you should see an output similar to the one below: