I'm debating on the best approach of sending code to clients.
Currently thinking of creating a github organization and inviting them to it but they are not too tech savvy.
I'd also like to exercise privacy if possible
How do you guys normally send code to clients?
1–6 of 6 posts
Re: How do you guys normally send code to clients?
#2For "not too tech savvy" clients, we take over the operations as well. How is this code deployed exactly? If they have their ops team, you should be talking to the ops team. If they don't, you should be asking them how will they be handling ops, and if they don't know what ops is, you should be explaining them what ops is, demonstrating that you can do it, and charging them for it.
Re: How do you guys normally send code to clients?
#3If they're not tech savvy, what are they going to do with the code? Is it just a required deliverable?
I always just save a copy of the repo (usually we make a special "deliverables" branch), delete the .git and zip it and put it on our MFT server, for which I provide the customer a login.
Re: How do you guys normally send code to clients?
#4For "not too tech savvy" clients, we take over the operations as well. How is this code deployed exactly? If they have their ops team, you should be talking to the ops team. If they don't, you should be asking them how will they be handling ops, and if they don't know what ops is, you should be explaining them what ops is, demonstrating that you can do it, and charging them for it.
We're still developing continuously.
Website is deployed on Vercel, I own the current GitHub repo which is integrated with Vercel.
I don't really want to make a Vercel team and add them to it, or add them to the repo. But they'd like a way to have the code as it changes.
Re: How do you guys normally send code to clients?
#5If they're not tech savvy, what are they going to do with the code? Is it just a required deliverable? I always just save a copy of the repo (usually we make a special "deliverables" branch), delete the .git and zip it and put it on our MFT server, for which I provide the customer a login.
Yeah they'd like access to code. The issue is we're still making changes, and will probably continue making changes for some time.
Re: How do you guys normally send code to clients?
#6For "not too tech savvy" clients, we take over the operations as well. How is this code deployed exactly? If they have their ops team, you should be talking to the ops team. If they don't, you should be asking them how will they be handling ops, and if they don't know what ops is, you should be explaining them what ops is, demonstrating that you can do it, and charging them for it.
We're still developing continuously. Website is deployed on Vercel, I own the current GitHub repo which is integrated with Vercel. I don't really want to make a Vercel team and add them to it, or add them to the repo. But they'd like a way to have the code as it changes.
Why not add them to the repo as read-only? Seems like the most straightforward approach.