4 ms·
Set up a virtualenv with defined versions of all dependencies, on install the python code there. And tar up the virtualenv. Or create a .deb or .rpm package ou
by perlgeek 11y ago
Set up a virtualenv with defined versions of all dependencies, on install the python code there. And tar up the virtualenv.
Or create a .deb or .rpm package out of the python code.
In a non-trivial setup, just doing a 'git checkout' isn't enough for a deployment.
- StavrosK 11y agoI'll just point out that your assumption that I'm only doing a "git checkout" is completely unwarranted.
- twic 11y agoGiven that in the comment to which that was a reply, you opined that 'It doesn't seem like setting up a build server just to do "git checkout; rm .git" is worth the effort.', it's not completely unwarranted.
- StavrosK 11y agoThe part that the build server can handle is the "git checkout" part, maybe create a virtualenv with the dependencies. In that case, doing a "git checkout" is enough for deployment, because you're already assuming that the rest of the deployment happens elsewhere.