How do people package internal software to their production servers?

Question

We build .deb packages and host them in a local Debian APT Repository, which we then use Puppet to manage installs from.

However, there is surprisingly little written about building or managing an apt repository, so I fear we're overlooking some beautiful open-source solution. What do other startups use? Do they just scp the raw files from server to server? If so, how do they keep things tidy?

Or is this a question that Rails handles internally (e.g. as gems) so we're the only ones facing it? ;)

score 3 · Accepted Answer · answered Mar 10 '11 at 18:56

3

I've worked at a number of startups and built a portage overlay for Gentoo, yum repo for CentOS, and most recently apt repo for Ubuntu. I too was surprised how much of a pain in the ass it was to build the apt repo and there was nearly nothing on the web about how to do it properly.

However in order to push website code we ultimately do some form of rsync and move the symlink. It's faster and easier to roll back in most cases.

answered Mar 10 '11 at 18:56

kashani

3,922
18
18

Yes, that's exactly what I've found, that it's surprisingly difficult to build and manage the apt repo and nobody seems to be talking about it. Thanks for reassuring me that I'm not overlooking something. – mrisher Mar 11 '11 at 05:07

score 2 · Answer 2 · edited Apr 13 '17 at 12:14

2

This page may be useful information about how to create an apt repository.

Also, have a look at this ServerFault thread linked in the comments.

edited Apr 13 '17 at 12:14

Community

1

answered Mar 10 '11 at 18:28

anthonysomerset

3,983
2
20
24

How do people package internal software to their production servers?

2 Answers2