fix: permission error.

[mugioka]

Summary

Now, accessing to demo site(https://demo.viron.plus) returns 503 due to container is not started.

This is because that /example/nodejs/.npm folder created with root owned folder.

So, we need to define USER node before RUN npm install in Dockerfile.

updated folder permission is bellow:

node@182909fc783b:~$ ls -al
total 1020
drwxr-xr-x   1 node node   4096 Jan  8 16:22 .
drwxr-xr-x   1 node node   4096 Jan  8 15:44 ..
drwxr-xr-x   3 node node   4096 Jan  8 16:20 .cache
drwxr-xr-x   1 node node   4096 Jan  8 16:18 .npm
drwxr-xr-x   2 node node   4096 Jan  8 15:28 cert
drwxr-xr-x  14 node node   4096 Jan  8 16:22 dist
drwxr-xr-x 679 node node  20480 Jan  8 16:20 node_modules
-rw-r--r--   1 node node 982233 Jan  8 16:20 package-lock.json
-rw-r--r--   1 node node   3771 Jan  8 15:28 package.json
drwxr-xr-x  15 node node   4096 Jan  8 15:28 src
-rw-r--r--   1 node node    825 Jan  8 15:28 tsconfig.json
-rw-r--r--   1 node node     62 Jan  8 15:28 tsconfig.production.json

Switch to the Preview mode and choose a PR template.

Read the Contribution guideline.

• General to create any kind of PRs except for versioning.
• Version to set new version for packages.

---

NOTE: This is a workaround for this

[changeset-bot[bot]]

⚠️ No Changeset found

Latest commit: 082b832794fa90ee251ee2aa59ddd79ef282056c

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR