Let's deploy via Git • Hacker News Board

Re: Let's deploy via Git

#111

Post by kyrias » Tue, Jun 25, 2013, 4:57 PM UTC

bradleyland wrote: post #107

eru wrote: post #102

Earlier quoted context omitted.

Shouldn't you audit all commits in any case?

So, you have two choices: 1) You can go through the trouble of identifying and resolving all the edge cases that you encounter when using Git as a deployment tool. Keeping in mind that one of those may result in an embarrassing security disclosure. Woops. 2) You can use a deployment tool that was developed for that purpose, has existed for years, and has had many sets of eyes on it; many of which are inevitably more…

If anything you should have the webroot directory in the git repo, not have the repo be the webroot

Re: Let's deploy via Git

#112

Post by inthewind » Tue, Jun 25, 2013, 6:09 PM UTC

Was looking for an email address for the author! And failed. Anyway just wanted to comment - that there's no publish date attached to the article - or one that is at least obvious. I have no idea when it was authored.

Re: Let's deploy via Git

#113

Post by robinson-wall » Sat, Jun 29, 2013, 11:42 PM UTC

AgentIcarus wrote: post #43

robinson-wall wrote: post #34

Earlier quoted context omitted.

> Install with native package tool I'm sad that so few people seem to build native OS packages for deployments. My build system creates a release package and sticks it in an apt repo, then puppet installs latest version of package when it runs.

I've just started looking at this sort of thing - can I ask what technology you decided on for the apt repo? (I'm especially interested in whether the restriction most of them impose on having multiple versions of a package is something you are dealing with).

Late reply, sorry. I went with reprepro to maintain my apt repo.

It's nice, but has one major drawback which may be a showstopper, depending on your use case. It can only keep one version of a package at a time in each distribution.