🐳 Developing a Pluto Application in Container

docker run -it --privileged \
    -v /var/run/docker.sock:/var/run/docker.sock \
    -v /lib/modules:/lib/modules \
    --name pluto-k3d \
    plutolang/pluto:latest-k3d bash

After creation, you'll automatically enter the container. Inside the container, execute the following command to automatically create a k3s cluster and install Knative. The last parameter is the cluster name, which you can change to another name:

bash /scripts/create-cluster.sh pluto-cluster

After the command completes, you should be able to see the k3s cluster nodes by executing:

kubectl get nodes

npm install
pip install -r ./requirements.txt

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

During deployment, Pluto will package several functions in the application into container images and upload them to the specified image repository. During the cluster creation process, a local image repository was automatically created by the script. The repository name consists of the cluster name plus -registry, and the port is 5432, for example, pluto-cluster-registry:5432.

Next, we'll 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), and modify the configs field by filling in the image repository address as follows:

...
stacks:
  - name: dev
    configs:
      kubernetes:registry: pluto-cluster-registry:5432
      kubernetes:platform: auto
...

In the K3s cluster, we can expose the service to the local environment using the kubectl port-forward command and then test the service with the curl command. You can execute the following command in the background to run kubectl port-forward, 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 if the service is working properly by executing the two commands below. hello-pluto-dev-plutolang-pluto-router-router.localdev.me is the access address output at the end of the Pluto 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 the deployment is successful, you should see output similar to the following:

Execute the following command to take down the Pluto application from the k3s cluster:

pluto destroy

If you want to delete the k3s cluster, you can execute the following command, and you need to change the cluster name to your own:

k3d cluster delete pluto-cluster

If you want to destroy the development environment, you can execute the following commands on the host machine:

docker stop pluto-k3d
docker rm pluto-k3d