How to paywall 💰 a private github repo
HTML-код
- Опубликовано: 29 апр 2024
- My Products
📖 ProjectPlannerAI: projectplannerai.com
🤖 IconGeneratorAI: icongeneratorai.com
📝 ThumbnailCritique: thumbnailcritique.com
Useful Links
💬 Discord: / discord
🔔 Newsletter: newsletter.webdevcody.com/
📁 GitHub: github.com/webdevcody
📺 Twitch: / webdevcody
🤖 Website: webdevcody.com
🐦 Twitter: / webdevcody
Today I learn 👌. I see you’re trying to break the Guiness world record for the most side projects
Its incredible how much I have learned from watching your content for the past year
glad to hear that!
Nice, this flow for github is being used a lot lately
You are so helpful it's insane
Good job babe!!
If you have done any RBAC could you show how it is done in next.js sometime? I am having issues with implementation for it in Auth0 but even if you dont use Auth0 ever, would be very cool
how do you protect the project from someone who bought access just forking and making it public?
I also have a starter kit. What I did was add a custom username field to the stripe checkout directly.
Its skipping one step, people without github account cant even buy it and then I do the same responding to the webhook as you do.
Yeah that’s a good idea
Just curious, is this project based on Marc Lou's "ShipFast"?
the idea for sure
I've seen a lot of starter kit products, and honestly Marc's "ShipFast" was one of the last ones I stumbled upon. Folks have been selling boilerplates since a long time ago.
His revenue made me want to try making one, and I personally need one for my own stack. He uses daisy ui and other stuff I don’t care about
@@WebDevCody - yeah, it’s crazy good money he’s reporting. I’d thought about how swapping out any of the pieces would make another product. Especially the meta-framework piece.
Never buy a starter kit there a so much stuff on the internet. Sorry to say it
Awesome stuff. Quick question tho why not GitHub login so they don't have to type their handle and potentially type the wrong one?
I mean the general sign up could be via GitHub. So we already have their GitHub handle/id and can just auto add them as collaborate when stripe comes back with a webhook.
Yeah that’s a good point as well! I’m not sure if their GitHub username comes back in the login event or not, I’ll need to check
@@WebDevCody I believe it does I remember from auth I implemented with Lucia and Arctic
For scammer? That rip your accounts
@@gold-junge91 not sure I understand how you mean?
Does that only gove read only access to your private repo? I think qhen you add collaborators its full access?
I specified read access in the code, hopefully it does what I think it does
Hi Cody, can you show us how you handle drizzle migrations without losing the data on production? I have a hobby project but every-time the db changes, I lose all the data.
What are the steps you're following?
You should let it generate the migration scripts, inspect those manually, then run them
I was following an article from Neon for Drizzle. It has db:generate, db:migrate commands. @rahultech
Your method is great but have have two questions arising from this method:
- Is there a cap on how many people are able to be added to the project
- Isn't there a "confidentiality" issue with the roles displayed on github ? I believe you are able to see every other person with the same role in the repo, meaning that you would be able to see who bought the code as another client.
The good old zip behind a s3 does not seem that bad in that regard.
Have a great day :)
You bring up some good points! I guess I could provide a zip download as well if people don’t want their name attached to the git repo
There is no cap as far as the GitHub documentation says. The note mentions this for the "GitHub Free" plan, but this should correspond to all other plans minus Enterprise.
The problem with this approach is that Cody would have to make zip files everytime he pushes some changes and have a flow to download them.
@@rahultech77 Its fine, you can easily push to s3 on code changes with CI/CD tools nowadays
@@rahultech77 You can automate the whole process with GitHub Releases. Cody barely has to do anything once he sets it all up.
What stops a person from buying access to the private repository and then cloning / publishing it on a public repository?
There will be a non disclosure license inside providing he sets that up, so cloning and publishing the source (or using in any other way in breach of license) will be illegal. But like you say, just because it's illegal nothing is stopping you from doing it. But same way fraud is fraud whether you get caught or not, doesn't mean you should do it nor take the risk :)
nothing really - that's basically pirating. I'd just assume 99% of the people who buy the starter kit are good people, and the other 1% won't have a platform to promote the cloned repo anyway.
@@WebDevCody I understand, in any case I would not expose a private repository to the public. Sometimes happens to accidentaly push sensitive data (like passwords, access keys, etc) and then you would make them available to anyone who has access to the private repository as a collaborator. Not to mention that there is probably a limit to the number you can invite, but I'm not sure about that.
Rather I would produce a secure-controlled package (in some format) to send to the customer (in some way). Just my opinion 😅
Why don't you have them link their github accounts using oauth?
supabase would be cool to choose from
Eh yeah I’m not a fan of suoabase
BLender artists could def take a hit at that lol
fist