Closed pbrisbin closed 9 years ago
Some screenshots:
I feel like we probably want to have plans go in the database. We're almost certainly going to want them in there eventually so that we don't need to deploy to make changes to third party IDs and such, so it seems like it's better to build them out that way to begin with.
I feel like we probably want to have plans go in the database. We're almost certainly going to want them in there eventually ...
Is it going to be any harder to move them to the DB when we need that vs doing it now?
Is it going to be any harder to move them to the DB when we need that vs doing it now?
I feel like the more behavior we build around this, the harder it will be to change later. If you think it's significantly easier to bootstrap this way, I think that's alright; I just don't want to build too much around an assumption that we know won't hold true for very long.
I'm going to close this and re-open as a new PR with Plan
s actually in the DB as well the initial Stripe integration to charge for them.
Very rough draft. Needs copy and design.