Skip to content

infrastructure for service providers implementation  #197

Description

@lucianmat

Would make sense to have a generic support in ParseServer for communication services, like mailgun, twillio,etc, based on generic configuration infrastructure parameters ?

like :

var api = new ParseServer({
  databaseURI: databaseUri || 'mongodb://localhost:27017/dev',
  cloud: process.env.CLOUD_CODE_MAIN || __dirname + '/cloud/main.js',
  appId: process.env.APP_ID || 'myAppId',
  masterKey: process.env.MASTER_KEY || 'myMasterKey',
  providers : {
       mailGun : {
            service: 'mailgun',
            apiKey: process.env.MAILGUN_API_KEY || 'mg-MYMAILGUNKEY',
            domain: process.env.MAILGUN_DOMAIN || '[email protected]',
            fromAddress: process.env.MAIL_FROM_ADDRESS || 'My App <[email protected]>' 
       },
      twillio : {
      }
    }
});

Instead of hardcoding providers into ParseServer (index.js) ?

Activity

  1. gfosco commented on Feb 20, 2016

    @gfosco
    Contributor

    Looks like we're headed in that direction... will close this, please call out anything you have a problem with in a new issue. thanks. 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions