46bf5270df
These changes introduce a new "service" to the members api, which handles getting and creating subscriptions. This is wired up to get subscription information when creating tokens, and attaching information to the token, so that the Content API can allow/deny access. Behind the subscription service we have a Stripe "payment processor", this holds the logic for creating subscriptions etc... in Stripe. The logic for getting items out of stripe uses a hash of the relevant data as the id to search for, this allows us to forgo keeping stripe data in a db, so that this feature can get out quicker. |
||
|---|---|---|
| .. | ||
| common | ||
| fs | ||
| image | ||
| members | ||
| mobiledoc | ||
| promise | ||
| security | ||
| social | ||
| constants.js | ||
| ghost-version.js | ||
| request.js | ||