Docker volume mounted Cloud Code directory doesn't work

[drdaz]

Make sure these boxes are checked before submitting your issue -- thanks for reporting issues back to Parse Dashboard!

• [ * ] You're running version >=1.0.23 of Parse Dashboard.

• [ * ] You're running version >=2.3.2 of Parse Server.

• [ * ] You've searched through existing issues. Chances are that your issue has been reported or resolved before.

Environment Setup

docker-compose.yml, set up as follows, using 'volumes' mapping to inject Cloud Code:

version: "3"

volumes:
  myappdbdata:
  myappconfigdata:

services:
  # MongoDB
  myappdb:
    image: mongo:3.0.8
    volumes:
      - myappdbdata:/data/db
      - myappconfigdata:/data/configdb
  myapp-parse-server:
    image: parseplatform/parse-server:2.7.2
    environment:
      - PARSE_SERVER_MASTER_KEY=someString
      - PARSE_SERVER_APPLICATION_ID=myapp
      - VERBOSE=1
      - PARSE_SERVER_DATABASE_URI=mongodb://myappdb:27017/dev
      - PARSE_SERVER_URL=http://myapp-parse-server:1337/parse
      - PARSE_SERVER_CLOUD_CODE_MAIN = /parse-server/cloud/
    depends_on:
      - myappdb
    ports:
      - 5000:1337
    volumes:
      - ./cloud:/parse-server/cloud

Steps to reproduce

• Add some appropriate Cloud Code (main.js) to ./cloud/.
• docker compose up
• Make some call to trigger your Cloud Code.

The call fails.

I've tried adding some garbage to my main.js file which would otherwise cause some error output from parse-server. This yielded no result, so the server doesn't actually use the mapped files.

I've checked the /parse-server/cloud directory on the guest / container and it contains the expected files. It's confusing.

Any idea how to achieve this? Do I have to build a custom image to use Cloud Code?

[drdaz]

Sadly enough, the issue here was whitespace

PARSE_SERVER_CLOUD_CODE_MAIN = /parse-server/cloud/

should have been

PARSE_SERVER_CLOUD_CODE_MAIN=/parse-server/cloud/

Used 1.5 days chasing this; fml.

[flovilmart]

@drdaz I feel you! Any recommendation to make it easier?

[drdaz]

@flovilmart

The documentation around it is a little muddied; there's places in the docs where we have PARSE_SERVER_CLOUD_CODE_MAIN, and other places where we have PARSE_SERVER_CLOUD. Perhaps others too; it adds some uncertainty, and is an extra variable to check when brute-forcing the problem. What's actually working for me is this: PARSE_SERVER_CLOUD. I haven't checked if the other one works :)

There's also talk in the docs that suggests the default path for the CC entry point is /parse-server/cloud/main.js. That doesn't appear to be the case. The code doesn't get hit unless I set the PARSE_SERVER_CLOUD variable to that path.

[flovilmart]

Do you have the links to the docs? We should probably update them

[drdaz]

I haven't got all the references at hand; I'll try and drop them here if / when I come across them again.

The docker hub documentation uses PARSE_SERVER_CLOUD_CODE_MAIN though: https://hub.docker.com/r/parseplatform/parse-server/