Faster way of deploying compiled softwareProper manual deployment of a Java Application Server on Ubuntu Server 8.10 - LinuxHow to upgrade ClamAV on Ubuntu Hardy Heron 8.04 LTS?Best (easiest) way to update Ubuntu to Apache version 2.2.17?Scripting installation of a virtual package provider on Debian/UbuntuCan we install Natty package into Lucid?Compiling FreeTDS 0.91 on Ubuntu 11.04 x64Best practice to track custom software installations on Linux in /usr?Search for installed unavailable packages (backports and 3rd party)Why does updating puppet ppa not update puppet?On Debian, how to audit installed packages against packages in a particular repository?
Term for checking piece whose opponent daren't capture it
Thousands and thousands of words
Is floating in space similar to falling under gravity?
Where did the “vikings wear helmets with horn” stereotype come from and why?
What does the behaviour of water on the skin of an aircraft in flight tell us?
find the Integer value after a string from a file
SPI on stm32 won't work without pullup resistors and even then performs poorly
Can an old DSLR be upgraded to match modern smartphone image quality
Do creatures all have the same statistics upon being reanimated via the Animate Dead spell?
Mother abusing my finances
Team member doesn't give me the minimum time to complete a talk
Are UK pensions taxed twice?
Could I be denied entry into Ireland due to medical and police situations during a previous UK visit?
Creating Fictional Slavic Place Names
The deliberate use of misleading terminology
Can non-English-speaking characters use wordplay specific to English?
Can a non-EU citizen travel within the Schengen area without identity documents?
Beginner's snake game using PyGame
What does "Marchentalender" on the front of a postcard mean?
Expenditure in Poland - Forex doesn't have Zloty
How to properly maintain eye contact with people that have distinctive facial features?
Should I run RG8x / mini8 zip tied to a cat 5e ethernet cable?
Is there an evolutionary advantage to having two heads?
How can I grammatically understand "Wir über uns"?
Faster way of deploying compiled software
Proper manual deployment of a Java Application Server on Ubuntu Server 8.10 - LinuxHow to upgrade ClamAV on Ubuntu Hardy Heron 8.04 LTS?Best (easiest) way to update Ubuntu to Apache version 2.2.17?Scripting installation of a virtual package provider on Debian/UbuntuCan we install Natty package into Lucid?Compiling FreeTDS 0.91 on Ubuntu 11.04 x64Best practice to track custom software installations on Linux in /usr?Search for installed unavailable packages (backports and 3rd party)Why does updating puppet ppa not update puppet?On Debian, how to audit installed packages against packages in a particular repository?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
I'm working on a project where I will have to deploy a large number of servers with particular software upon them. At the moment, I'm able to use the standard Ubuntu repositories, however the version of the software that is on these repos (v1.0) is considerably older than the current version available from the developers (v.1.5.6). That leaves me downloading the source, and then building locally on each server that I intend on sending out the door. It takes about an hour to build this one particular piece of software, so I got to thinking that there's a better way of doing things.
In Googling such a solution, I see that there are a number of possibilities out there, but I wanted to get others take on whether or not I'm going down the right path, or not. If I understand this correctly, I can create a package and then place it on either a PPA (which I believe would be publicly available) or on a private repo that I could stand up. Either option would be fine really, this isn't my software I'm merely compiling it and making it available for myself and others to use.
It's my understanding then that, as long as all my servers have the same version of Ubuntu upon them, architecture etc, I could point them to this new resource and use aptitude to install the software, without having to go through the pains (and time) of compiling.
Is this generally correct? Am I over-simplifying? Is there a better way of achieving the same result?
(Cross post from here)
ubuntu apt packages
asked May 15 at 21:11
bnoeafkbnoeafk
82
add a comment |
I'm working on a project where I will have to deploy a large number of servers with particular software upon them. At the moment, I'm able to use the standard Ubuntu repositories, however the version of the software that is on these repos (v1.0) is considerably older than the current version available from the developers (v.1.5.6). That leaves me downloading the source, and then building locally on each server that I intend on sending out the door. It takes about an hour to build this one particular piece of software, so I got to thinking that there's a better way of doing things.
In Googling such a solution, I see that there are a number of possibilities out there, but I wanted to get others take on whether or not I'm going down the right path, or not. If I understand this correctly, I can create a package and then place it on either a PPA (which I believe would be publicly available) or on a private repo that I could stand up. Either option would be fine really, this isn't my software I'm merely compiling it and making it available for myself and others to use.
It's my understanding then that, as long as all my servers have the same version of Ubuntu upon them, architecture etc, I could point them to this new resource and use aptitude to install the software, without having to go through the pains (and time) of compiling.
Is this generally correct? Am I over-simplifying? Is there a better way of achieving the same result?
(Cross post from here)
ubuntu apt packages
asked May 15 at 21:11
bnoeafkbnoeafk
82
Please don’t cross post - But yes generally creating your own package is the easiest method of distributing pre-compiled software over a number of servers. Creating your own repo is not always necessary (for instance simply copying the package and installing it locally from your configuration mgmt software is another alternative)
– HBruijn
May 15 at 22:06
add a comment |
I'm working on a project where I will have to deploy a large number of servers with particular software upon them. At the moment, I'm able to use the standard Ubuntu repositories, however the version of the software that is on these repos (v1.0) is considerably older than the current version available from the developers (v.1.5.6). That leaves me downloading the source, and then building locally on each server that I intend on sending out the door. It takes about an hour to build this one particular piece of software, so I got to thinking that there's a better way of doing things.
In Googling such a solution, I see that there are a number of possibilities out there, but I wanted to get others take on whether or not I'm going down the right path, or not. If I understand this correctly, I can create a package and then place it on either a PPA (which I believe would be publicly available) or on a private repo that I could stand up. Either option would be fine really, this isn't my software I'm merely compiling it and making it available for myself and others to use.
It's my understanding then that, as long as all my servers have the same version of Ubuntu upon them, architecture etc, I could point them to this new resource and use aptitude to install the software, without having to go through the pains (and time) of compiling.
Is this generally correct? Am I over-simplifying? Is there a better way of achieving the same result?
(Cross post from here)
ubuntu apt packages
asked May 15 at 21:11
bnoeafkbnoeafk
82
I'm working on a project where I will have to deploy a large number of servers with particular software upon them. At the moment, I'm able to use the standard Ubuntu repositories, however the version of the software that is on these repos (v1.0) is considerably older than the current version available from the developers (v.1.5.6). That leaves me downloading the source, and then building locally on each server that I intend on sending out the door. It takes about an hour to build this one particular piece of software, so I got to thinking that there's a better way of doing things.
In Googling such a solution, I see that there are a number of possibilities out there, but I wanted to get others take on whether or not I'm going down the right path, or not. If I understand this correctly, I can create a package and then place it on either a PPA (which I believe would be publicly available) or on a private repo that I could stand up. Either option would be fine really, this isn't my software I'm merely compiling it and making it available for myself and others to use.
It's my understanding then that, as long as all my servers have the same version of Ubuntu upon them, architecture etc, I could point them to this new resource and use aptitude to install the software, without having to go through the pains (and time) of compiling.
Is this generally correct? Am I over-simplifying? Is there a better way of achieving the same result?
(Cross post from here)
ubuntu apt packages
ubuntu apt packages
asked May 15 at 21:11
bnoeafkbnoeafk
82
asked May 15 at 21:11
bnoeafkbnoeafk
82
asked May 15 at 21:11
bnoeafkbnoeafk
82
asked May 15 at 21:11
bnoeafkbnoeafk
82
asked May 15 at 21:11
bnoeafkbnoeafk
82
82
Please don’t cross post - But yes generally creating your own package is the easiest method of distributing pre-compiled software over a number of servers. Creating your own repo is not always necessary (for instance simply copying the package and installing it locally from your configuration mgmt software is another alternative)
– HBruijn
May 15 at 22:06
add a comment |
Please don’t cross post - But yes generally creating your own package is the easiest method of distributing pre-compiled software over a number of servers. Creating your own repo is not always necessary (for instance simply copying the package and installing it locally from your configuration mgmt software is another alternative)
– HBruijn
May 15 at 22:06
Please don’t cross post - But yes generally creating your own package is the easiest method of distributing pre-compiled software over a number of servers. Creating your own repo is not always necessary (for instance simply copying the package and installing it locally from your configuration mgmt software is another alternative)
– HBruijn
May 15 at 22:06
Please don’t cross post - But yes generally creating your own package is the easiest method of distributing pre-compiled software over a number of servers. Creating your own repo is not always necessary (for instance simply copying the package and installing it locally from your configuration mgmt software is another alternative)
– HBruijn
May 15 at 22:06
add a comment |
1 Answer
1
active
oldest
votes
Yes, compiling a deb package is how you can install a single build to many hosts.
Many ways to distribute and install this package, including maintaining your own private apt repo.
If open source, yes you can create a public PPA and use that as your apt repo. Any distribution welcomes package maintainers.
answered May 15 at 22:11
John MahowaldJohn Mahowald
10.3k1714
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "2"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f967465%2ffaster-way-of-deploying-compiled-software%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Yes, compiling a deb package is how you can install a single build to many hosts.
Many ways to distribute and install this package, including maintaining your own private apt repo.
If open source, yes you can create a public PPA and use that as your apt repo. Any distribution welcomes package maintainers.
answered May 15 at 22:11
John MahowaldJohn Mahowald
10.3k1714
add a comment |
Yes, compiling a deb package is how you can install a single build to many hosts.
Many ways to distribute and install this package, including maintaining your own private apt repo.
If open source, yes you can create a public PPA and use that as your apt repo. Any distribution welcomes package maintainers.
answered May 15 at 22:11
John MahowaldJohn Mahowald
10.3k1714
add a comment |
Yes, compiling a deb package is how you can install a single build to many hosts.
Many ways to distribute and install this package, including maintaining your own private apt repo.
If open source, yes you can create a public PPA and use that as your apt repo. Any distribution welcomes package maintainers.
answered May 15 at 22:11
John MahowaldJohn Mahowald
10.3k1714
Yes, compiling a deb package is how you can install a single build to many hosts.
Many ways to distribute and install this package, including maintaining your own private apt repo.
If open source, yes you can create a public PPA and use that as your apt repo. Any distribution welcomes package maintainers.
answered May 15 at 22:11
John MahowaldJohn Mahowald
10.3k1714
answered May 15 at 22:11
John MahowaldJohn Mahowald
10.3k1714
answered May 15 at 22:11
John MahowaldJohn Mahowald
10.3k1714
answered May 15 at 22:11
John MahowaldJohn Mahowald
10.3k1714
10.3k1714
add a comment |
add a comment |
Thanks for contributing an answer to Server Fault!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f967465%2ffaster-way-of-deploying-compiled-software%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Please don’t cross post - But yes generally creating your own package is the easiest method of distributing pre-compiled software over a number of servers. Creating your own repo is not always necessary (for instance simply copying the package and installing it locally from your configuration mgmt software is another alternative)
– HBruijn
May 15 at 22:06