Asking for help from docker experts re custom extensions issue

[Hyperbytes]

Background for info
As many of you know, i do not use docker day to day, personally prefering the VPS/FTP route.

However, recently i found myself in need to the use of UUIDs as primary keys in a project and found the known issue with knex() and MySql not returning UUID identities on insert problematic.
So i decided to go the Docker route and use PostgreSQL.

The Problem
All went without issues until I went to install one of my own server extensions.
The extension appeared to install when installed form the Project/Extensions tab but i could not see the extension in the Server connect list.
I then went to check for the node module and noticed that there is no node_modules folder when using docker (intrigued as to why it's not necessary)

After several restarts i manually installed the files in the extensions/server_connect_modules folder which worked correctly but is far from ideal.
Is there something additional i need to do to make my extensions compatible with Docker?
Can't believe nobody from the 100s of downloads has highlighted this issue to me.
(not yet tested in production, development only)

[guptast]

Hi Brian,

@Hyperbytes

I then went to check for the node module and noticed that there is no node_modules folder when using docker (intrigued as to why it's not necessary)

This is what I understand from building and deploying web apps via Docker in Wappler.

When deploying a project in Docker (locally or remotely), the node modules are installed via the package.json file. Basically, everytime a project is deployed via Docker, it installs the packages.

There are two files that drive this process: docker-compose.yml and Dockerfile. Both files are available here .wappler > targets > target_name > docker-compose.yml and .wappler > targets > target_name > web > Dockerfile.

@Hyperbytes

The extension appeared to install when installed form the Project/Extensions tab but i could not see the extension in the Server connect list.

I don't think this is related to Docker or the absence of node_modules folder. I have come across this issue where the extension was installed correctly, but it didn't add any npm modules and files in the extensions/server_connect_modules folder that were needed to run this extension. I had to manually copy the files and add the npm module in the package.json file before re-deploying the docker project.

At the time, I thought it was something wrong with my setup, but it seems it may be an issue or a bug with the installation of extensions itself.

[Hyperbytes]

Thanks
did check docker-compose.yml and Dockerfile after finding this post.

Docker(nodejs) doesn't recognise custom node module installations

Just installed nanoid package in my brand new docker container. Although package.json has the dependency and it is in the node_modules folder Wappler app isn’t able to find it. [image] [image] [image]

@guptast

but it didn't add any npm modules and files in the extensions/server_connect_modules folder that were needed to run this extension. I had to manually copy the files and add the npm module in the package.json file before re-deploying the docker project.

Exactly as I have just found

In the above post I ahve just found JonL suggests a fix which @George later reports as "improved"
My dockercompose.yml does have that recommendation added

'../../../extensions:/opt/node_app/extensions'

but still not working:

services:
  web:
    volumes:
      - '../../../app:/opt/node_app/app'
      - '../../../lib:/opt/node_app/lib'
      - '../../../views:/opt/node_app/views'
      - '../../../public:/opt/node_app/public'
      - '../../../extensions:/opt/node_app/extensions'
      - '../../../db:/opt/node_app/db'
      - '../../../certs:/opt/node_app/certs'
      - '../../../public/userdata:/opt/node_app/public/userdata:rw'
    ports: