-
Notifications
You must be signed in to change notification settings - Fork 95
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
Supporting multiple sites #172
Comments
@rizo Is the only thing you need out of the new site a different gateway? We have processes in place through support to migrate a site from one gateway to another. Perhaps that would be a simpler solution for you all? |
@NiceMLT thanks for the quick reply! The payment gateway used by our production Chargify site is Windcave. We have asked them to help us migrate the data to Stripe, but unfortunately they refused to do it. So we think that the only option that we have now is to migrate our customers manually. Could you give me more information on how your support team could help us with this? |
Hey @rizo no problem at all. I'm "just" a developer here but I've worked with our support team before on merchants migrating from one gateway to another. We do it frequently enough that there are processes in place for it with our support team. Let me see if I can get someone to reach out to you all. |
I'm working on a project that is transitioning from one Chargify site to another Chargify site (powered by a different payment gateway). In order to execute this migration, without disrupting the existing payment flows, we decided to support two Chargify sites in parallel.
Unfortunately it seems like
chargify_api_ares
gem does not support this. In particular, currently the configuration is defined as a singleton in a module, preventing the consumers from having multiple instances.Are there any plans to change this behaviour? If not, could you recommend any alternative approaches to use
chargify_api_ares
in a project with two Chargify sites?Thanks in advance!
The text was updated successfully, but these errors were encountered: