Fixes parse-community#1334 by resolving relative cloud code file path…

…s to the process' working directory.
airdrummingfool · Apr 4, 2016 · 8445d76 · 8445d76
1 parent 7462007
commit 8445d76
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 2 deletions.
diff --git a/spec/helper.js b/spec/helper.js
@@ -10,7 +10,7 @@ var ParseServer = require('../src/index').ParseServer;
 var path = require('path');
 
 var databaseURI = process.env.DATABASE_URI;
-var cloudMain = process.env.CLOUD_CODE_MAIN || '../spec/cloud/main.js';
+var cloudMain = process.env.CLOUD_CODE_MAIN || './spec/cloud/main.js';
 var port = 8378;
 
 // Default server configuration for tests.

diff --git a/src/ParseServer.js b/src/ParseServer.js
@@ -9,6 +9,7 @@ var batch = require('./batch'),
     middlewares = require('./middlewares'),
     multer = require('multer'),
     Parse = require('parse/node').Parse,
+    path = require('path'),
     authDataManager = require('./authDataManager');
 
 import { logger,
@@ -140,7 +141,7 @@ class ParseServer {
       if (typeof cloud === 'function') {
         cloud(Parse)
       } else if (typeof cloud === 'string') {
-        require(cloud);
+        require(path.resolve(process.cwd(), cloud));
       } else {
         throw "argument 'cloud' must either be a string or a function";
       }