2 ms·
Suppose you've invested in a build server anyway, for CI. Then you can just add/extend a job to create a release package, and deploy it. Doesn't take that muc
by shoo 11y ago
Suppose you've invested in a build server anyway, for CI.
Then you can just add/extend a job to create a release package, and deploy it.
Doesn't take that much effort, and lets you avoid infecting your production boxes with dev infrastructure/scaffolding, as `NickNameNick` suggests.
- StavrosK 11y agoWhat sort of def scaffolding do you mean? The benefits of just pulling the repo are that you can use ansible-pull to automatically update the servers whenever new code is merged to master, which would be more complicated if you had the CI server doing the pushing.
- shoo 11y ago> What sort of def scaffolding do you mean? version control software, to start with. perhaps more. i guess my viewpoint is coloured as the last thing i was working on was deployed to client desktop machines. there was absolutely no way we were going to be pushing to those with version control. if you are deploying to a server you own, i guess in principle you can do whatever you want. one of my colleagues rigged a build to create a debian package for the server-side version of the code we worked on. that took a bit of mucking about to get going but was very nice when it was set up.
- StavrosK 11y agoBuilding a deb is also an option, I generally don't prefer it because just pulling is easier to set up, and debs don't have that many advantages when you're dealing with interpreted server code.