Pass different configurations to coderunner deploy

rmaturi · November 20, 2019, 6:15pm

Backendless Version (3.x / 5.x, Online / Managed / Pro )

Online

Client SDK (REST / Android / Objective-C / Swift / JS )

REST

Question

Is it possible to pass different configuration files, probably different coderunner.json files to the coderunner executable?

I have a couple of environments and I’m doing npm run deploy to deploy my changes to that specific environment, but would be nice to do something like npm run deploy --production so the coderunner deploys to the correct invironment.

I see the coderunner.json file has the application id in there so I’ve been changing the values back and forth to deploy to the corresponding environment but would be great if I can do this automatically.

mark-piller · November 20, 2019, 6:46pm

Hi Racardo,

It is possible to do it with the -c <path> parameter. You can see a list of all available parameters at:

github.com

Backendless/JS-Code-Runner/blob/master/lib/cli/clirunner.js#L139


  appRequired     : true,
  showVersion     : true,
  showCopyright   : true,
  showModelConfirm: true
})


process.title = 'Backendless CodeRunner for JS'


program
  .version(packageConfig.version)
  .option('-c, --config <path>', 'set config path. defaults to ./coderunner.json')
  .option('-a, --app-id <id>', 'Application Id')
  .option('-k, --app-key <key>', 'Application CodeRunner API Key')
  .option('-s, --api-server <url>', 'Backendless API Server URL')
  .option('-m, --model <model>', 'Business Logic model')
  .option('-q, --quiet', 'Don\'t show the confirmation dialog before deploy to Business Logic model')
  .option('--msg-broker-host <host>', 'Message Broker Host')
  .option('--msg-broker-port <port>', 'Message Broker Port')
  .option('--repo-path <path>', 'Backendless Repo Path')
  .option('--cache-limit <n>', 'Count for cached workers')
  .option('--keep-zip', 'Keep generated zip file after deploying')

Alternatively, you can modify package.json as shown below:

"scripts": {
    "debug": "coderunner debug",
    "deploy": "coderunner deploy"
    "deploy:prod": "coderunner deploy --config ./coderunner-prod.json"
  },
...

And then run npm run deploy:prod to launch that configuration.

Hope this helps.

Regards,
Mark

rmaturi · November 21, 2019, 12:19am

This is exactly what we needed! Thanks a lot for the information Mark! Good to know the coderunner supports all these parameters.