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

Cybs.ini should be picked up from current or configurable directory #19

Open
brianmc opened this issue Sep 24, 2015 · 3 comments
Open

Comments

@brianmc
Copy link
Contributor

brianmc commented Sep 24, 2015

Having cybs.ini inside the sdk itself is great for tests and built-in samples but you really want to have the configuration within your application. In addition if you use something like Azure/heroku auto-deploys you really can't change anything in the SDK/vendor dirs.

What I was able to do to work around was just set the include path to the current dir, where my config was and maybe that's enough if it is documented.

set_include_path(getcwd());

@thwiv
Copy link

thwiv commented Nov 30, 2015

I would say the better workaround is to write a class that extends CybsClient and then write your own constructor. This also allows you to have more than one CyberSource account if need be.

@jrgonzalezrios
Copy link

@thwiv That worked for me, thanks

@gmorosdev
Copy link

I would say the better workaround is to write a class that extends CybsClient and then write your own constructor. This also allows you to have more than one CyberSource account if need be.

I agree with @thwiv, the package sould support manage more than one business account

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

4 participants