canmove, Confirmed users
6,439
edits
ReleaseEngineering/OPSI: Difference between revisions
→Creating a package
Lukasblakk (talk | contribs) (added production opsi IP) |
|||
| Line 119: | Line 119: | ||
====Testing the package on staging==== | ==== Testing the package on staging ==== | ||
On staging you want to test out the package first to make sure it installs correctly before it goes into production. | On staging you want to test out the package first to make sure it installs correctly before it goes into production. | ||
To create a .opsi package and inform OPSI about it, do the following: | To create a .opsi package and inform OPSI about it, do the following: | ||
(For staging): | (For staging): | ||
# as root on the opsi server | # as root on the opsi server | ||
opsi- | cd ~cltbld/opsi-package-sources | ||
su -c './regenerate-package dir-with-your-package' | |||
If there are any issues and you need to regenerate the package you can simply drop in the new code and run the above again. | |||
If there are any issues and you need to regenerate the package you can | |||
=== Installing the package file on production === | === Installing the package file on production === | ||