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

Makes Stripe integration optional #182

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

michaelwschultz
Copy link

Description

Stripe seems like it isn't necessary right now and in fact something that is a deterrent for local development. For now, I commented out the place it's used so it can be brought back easily. Not sure that commented code follows the current guidelines. If so, happy to remove it altogether.

I also left the env variables in the .env.example but made it clear they are optional. They are still required by the type checker, but since there are defaults, I thought this would be fine. This makes commenting out the code simple as well since there isn't a bunch of stuff that needs to be removed in order to satisfy the removal of the env variables.

What type of PR is this? (check all applicable)

  • πŸ’‘ Feature
  • πŸ› Bug Fix
  • πŸ“ Documentation Update
  • 🎨 Style
  • πŸ§‘β€πŸ’» Code Refactor
  • πŸ”₯ Performance Improvements
  • βœ… Test
  • πŸ€– Build
  • πŸ” CI
  • πŸ“¦ Chore (Release)
  • ⏩ Revert

Related Tickets & Documents

Closes: #112

Mobile & Desktop Screenshots/Recordings

Steps to QA

  1. visit dashboard
  2. bask in the glory of the ability to see your dashboard without needing Stripe env variables

Added to documentation?

  • πŸ“œ README.md
  • πŸ™… no documentation needed

[optional] Are there any post-deployment tasks we need to perform?

[optional] What gif best describes this PR or how it makes you feel?

by for now

Copy link

vercel bot commented Feb 28, 2024

@michaelwschultz is attempting to deploy a commit to the Salgsmaskin Team on Vercel.

A member of the Team first needs to authorize it.

Copy link
Member

@alexghirelli alexghirelli left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure it's the best way commenting the Stripe part. Maybe can be more elegant adding an env var that can specifies if you are self hosting or not the project. I mean, it can be a boolean something like "SELF_HOST:true|false" and inside the code in each points where we are using Stripe we can wrap them by checking if this env var is true or false. If it's true Stripe logic will be avoided otherwise it will be enabled and triggered.

@michaelwschultz
Copy link
Author

I guess I'm curious if Stripe is even needed at this point. Is there a product write up anywhere that talks about what is needed for MVP?

@akinwol akinwol added this to the Alpha 0.1 milestone Mar 4, 2024
@akinwol
Copy link
Collaborator

akinwol commented Mar 4, 2024

@michaelwschultz I dont think stripe is needed at this point. We should just remove the dependency for it for now (just my thought)

@alexghirelli
Copy link
Member

@michaelwschultz I dont think stripe is needed at this point. We should just remove the dependency for it for now (just my thought)

We only need Stripe in hosted version. So we can avoid it as I wrote days ago, via an env var.

@matteobad

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

Successfully merging this pull request may close these issues.

Bug: stripe: not found
3 participants