Create plaid.md #2419
Reference in New Issue
Block a user
Delete Branch "main"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Added instructions on how to set up plaid with your self hosted instance
@Facinorous-420 - nice work!
I've been doing some troubleshooting on selfhosted Plaid Sync today because my synced transactions only go back 3mos. I'm not sure it's related but - it's probably important to also note that in order for Plaid webhooks to work, your selfhosted server needs to be accessible from external networks. I don't think you need to set anything up for webhooks in the Plaid dashboard.
You can clearly see here webhook requests started to succeed after exposing my instance to the internet.
You are correct, your Maybe instance needs a FQD with SSL. Plaid does not work properly without this. I first tried a local domain with local SSL generated via mkcert, but of course Plaid doesn't have the DNS to see my custom domains so that didn't work.
It would be nice if we didn't have to expose our instances to the web, such as Actual is about to using Simplefin.
I can add a line regarding the need for external access, FQD, and SSL. :)
Love it! Thanks for the guide, I think a lot of self hosting folks will find this useful.
We've mentioned several times across our channels that our internal team does not have the capacity to officially support self-hosted Plaid, so we can't accept this into the main codebase. That said, we'll move it over to Community discussions and anyone who's looking to learn how to configure Plaid can reference it there.
@Facinorous-420 I just remembered that Github does not have a way to convert a Pull Request to a discussion, so I'm going to close this one out. I'd recommend copy/pasting this guide to a discussion.
Thanks. Created it here:
https://github.com/maybe-finance/maybe/discussions/2421
I must say, I was looking for a guide like this specifically in the docs of the repo because there was that docs folder.
It would be nice to have all documentation organized in 1 spot, rather than having it all over the place.
Thanks so much Zach for embracing the open and self-hosted-ness while drawing a clear line and providing a place where the community can and should continue support.
Hey @Facinorous-420 ... would you be interested in sending this to a new community fork we're trying to get going? Want to re-submit this PR there?
I am sure we could do what you mention above now that we're not worried about the "commercial support" angle:
Sure :)
I'll make the PR I once I get home from work.
Thank you! I could have cherry-picked your commit ... but helps get the repo going with activity if people submit directly. :-)
Pull request closed