You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 25, 2018. It is now read-only.
we have separate applications defined in Parse for our staging and development environments. in V1 of this library, we could pass the configuration paramaters when instantiating the parseRestClient class. This feature appears to be removed from V2 in favor of a configuration file.
Any suggestions?
The text was updated successfully, but these errors were encountered:
This scenario is exactly why I switched to a config file. Production, staging and dev environments can all have different parseConfig.php in each environment. This way you don't have to change your code when going from one environment to another.
We use zend framework and store all our config options in a single application.ini file for prod, stage and dev. zend allows us to dynamically load config params based on SERVER_NAME env var.
Its convenient to be able to instantiate a class by passing config params.
This scenario is exactly why I switched to a config file. Production, staging and dev environments can all have different parseConfig.php in each environment. This way you don't have to change your code when going from one environment to another.
—
Reply to this email directly or view it on GitHub.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
we have separate applications defined in Parse for our staging and development environments. in V1 of this library, we could pass the configuration paramaters when instantiating the parseRestClient class. This feature appears to be removed from V2 in favor of a configuration file.
Any suggestions?
The text was updated successfully, but these errors were encountered: