| 1 |
On Sat, 2005-09-10 at 14:29 -0500, John Jolet wrote: |
| 2 |
> We're in the process of transitioning from 32-bit Redhat (7 I think) web/app |
| 3 |
> servers to 64-bit gentoo web/app servers. One concern I've got is from a |
| 4 |
> security standpoint, normally you don't deploy webservers with development |
| 5 |
> tools on them. How do you guys handle this question with internet-facing |
| 6 |
> production servers? |
| 7 |
> |
| 8 |
> One thought I had was to set up a build server, build the binaries on this |
| 9 |
> server, and do an emerge of the binaries FROM this server to the production |
| 10 |
> servers, with gcc and such removed from them. Will this work? |
| 11 |
|
| 12 |
Yes. |
| 13 |
|
| 14 |
>From emerge(1): |
| 15 |
|
| 16 |
--buildpkg (-b) |
| 17 |
Tells emerge to build binary packages for all ebuilds processed |
| 18 |
in addition to actually merging the packages. Useful for main- |
| 19 |
tainers or if you administrate multiple Gentoo Linux systems |
| 20 |
(build once, emerge tbz2s everywhere). The package will be cre- |
| 21 |
ated in the ${PKGDIR}/All directory. An alternative for |
| 22 |
already-merged packages is to use quickpkg which creates a tbz2 |
| 23 |
from the live filesystem. |
| 24 |
|
| 25 |
I would recommend building packages on a build server with --buildpkg, |
| 26 |
installing them on a testing server, and once tested re-packaging them |
| 27 |
with quickpkg on the testing server to install on the production |
| 28 |
servers. (The advantage of quickpkg is it picks up changes to |
| 29 |
configuration files.) Of course, you could combine the build and testing |
| 30 |
servers onto one machine. |
| 31 |
|
| 32 |
HTH. |
| 33 |
|
| 34 |
-- |
| 35 |
gentoo-user@g.o mailing list |
Archives