Automate creation of the Convene pricing tier #26
Conversation
See: #8 I was using this primarily to explore what it would look like to build Product and Pricing setup into Compensated/Support, while also ensuring we have a papertrail for setting up pricing for Convene.
There was a problem hiding this comment.
I am confused on what we are trying to do here and some usage example might help me better understand.
Is bin/configure-pricing intended to be ran by developer and copy the output to zinc.coop?
Can you let me know your thoughts on how compensated would fit into this?
|
@user512 - Yep! Keep in mind, part of Convene's business strategy is we want folks to be comfortable setting up their own "franchise" of Convene. This way someone could have an Oakland City Convene or a New Zealand Convene. Franchisees pay Zinc for the right to use Convene within an LLC or other legal entity, while people who are willing to take on all the liability personally can use the Convene code free-of-charge to manage their own instances. The way I think compensated could fit in with this is documented in Developer Creates Products and Prices in Stripe. Essentially, we could help folks get started running a business by using compensated to manage their portfolio of products and prices across sales channels (Apple, Stripe, Android, etc). |
See: #79 The compensated cli now exists, and forwards options and configuration into commands. Commands can be defined by extending the `Compensated::Command` class, and overriding the `execute` method. The first command is `apply`, which creates the configured products and prices in the Payment Processors that support it. This is a pretty-close to direct port of the code that I wrote to allow folks to create products and prices in Stripe. See: zinc-collective/convene#26 Further, this gives us a `.rubocop.yml` file in the top level of the project so that formatting can begin to become consistent across files.
See: #79 The compensated cli now exists, and forwards options and configuration into commands. Commands can be defined by extending the `Compensated::Command` class, and overriding the `execute` method. The first command is `apply`, which creates the configured products and prices in the Payment Processors that support it. This is a pretty-close to direct port of the code that I wrote to allow folks to create products and prices in Stripe. See: zinc-collective/convene#26 Further, this gives us a `.rubocop.yml` file in the top level of the project so that formatting can begin to become consistent across files.
See: #79 The compensated cli now exists, and forwards options and configuration into commands. Commands can be defined by extending the `Compensated::Command` class, and overriding the `execute` method. The first command is `apply`, which creates the configured products and prices in the Payment Processors that support it. This is a pretty-close to direct port of the code that I wrote to allow folks to create products and prices in Stripe. See: zinc-collective/convene#26 Further, this gives us a `.rubocop.yml` file in the top level of the project so that formatting can begin to become consistent across files.
See: #8
I was using this primarily to explore what it would look like to build
Product and Pricing setup into Compensated/Support, while also ensuring
we have a papertrail for setting up pricing for Convene.