Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

infrastructure for service providers implementation #197

Closed
lucianmat opened this issue Feb 3, 2016 · 1 comment
Closed

infrastructure for service providers implementation #197

lucianmat opened this issue Feb 3, 2016 · 1 comment

Comments

@lucianmat
Copy link

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) ?

@gfosco
Copy link
Contributor

gfosco commented Feb 20, 2016

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
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants