3 ms·
My git "workflow" (if you can call it that) is to explicitly ban git from production systems. If your prod machine requires Git to get code, you're probably doi
by nameless912 10y ago
My git "workflow" (if you can call it that) is to explicitly ban git from production systems. If your prod machine requires Git to get code, you're probably doing something wrong. Config files are better gotten from an HTTP API, where you can audit access; actual code/program files are better grabbed from something like Artifactory or a network share.
- shaftway 10y agoI don't think it's all that bad, especially not for a small shop. I mean, obvious caveats aside. Don't store sensitive stuff like passwords in git, don't store big files. But it does provide a pretty simple clean deploy, with information about the state of your deployment. You can even include some of that audit support with some relatively simple, judicious scripts. Check out, echo something to a log file, commit it to a deployment branch and push it. I'm not sure I see how network shares or an http API offer better access controls over a git repo loaded over https for loading up code.