Difference between revisions of "How to Package Rifidi Edge"
From RifidiWiki
| Line 23: | Line 23: | ||
3. Navigate to the SDK folder in the terminal and type 'sh build.sh'. DO NOT use sudo. | 3. Navigate to the SDK folder in the terminal and type 'sh build.sh'. DO NOT use sudo. | ||
4. The deb will show up in sdk/rifidi/debian/Debian-packages | 4. The deb will show up in sdk/rifidi/debian/Debian-packages | ||
| − | 5. Immediately move the deb out of the Debian-packages and install it via "sudo dpkg -i (deb)". Test it and make sure everything is correct. | + | 5. Immediately move the deb out of the Debian-packages and install it via "sudo dpkg -i (deb)". Test it and make sure everything is correct. If you need to change anything, you'll probably need to hook up the SDK to SVN again (or delete and re-download it from SVN). |
=Server Only Zip= | =Server Only Zip= | ||
==Prerequisites== | ==Prerequisites== | ||
| + | 1. You'll need a debian package you are satisfied is working correctly to make the zip. | ||
==Steps== | ==Steps== | ||
| + | 1. Open the deb with an archive tool and extract the "rifidi" folder. | ||
| + | 2. Zip up the folder to a 7zip file with the name "RifidiEdge-XXX-server_only.7z", where XXX is the version number, like "3.1.0". | ||
=Windows Installer= | =Windows Installer= | ||
==Prerequisites== | ==Prerequisites== | ||
| + | 1. You need to be on windows to make the windows installer. | ||
| + | 2. You need the installer | ||
==Steps== | ==Steps== | ||
=SDK= | =SDK= | ||
Revision as of 03:46, 4 November 2014
Contents
Introduction
These are the prerequisites and steps for packaing the Rifidi Edge SDK, Deb, Server Only Zip and Windows Installer
It is best to export the versions in this order for release: 1. Deb 2. Server only 3. Windows Installer 4. SDK
You will need a windows and linux machine (or virtual machine) to export and test. Dropbox is invaluable for this purpose, as it allows you to easily share the files across different machines.
Deb
Prerequisites
1. You need to be on linux to build the Deb. 2. The docs, jars, bundles,info, rifidiserver.ini and rifidi-server linux executable must all be correct before release. Check them all before and after you export the deb or you will need to export it again. 3. bundles.info is very easy to get wrong. Test the deb as soon as you export it for the first time, and make sure all the bundles you are expecting to show up show up with the "ss" command. Debug and fix any that aren't working, fix the bundles.info in the SDK and rebuild. 4. Make sure the version numbers are incremented in "SDK/version.txt", "SDK/rifidi/usr/local/sbin/rifidi/version.txt", and "SDK/rifidi/debian/DEBIAN/control". 5. Make sure all your changes are checked in, as building the deb requires disconnecting the SDK from SVN.
Steps
1. Make sure you have a new, fully updated SDK in your workspace. 2. Disconnect the SDK project from SVN. Delete the SVN metadata. If all the exported documents are way too big, you forgot to do this step. 3. Navigate to the SDK folder in the terminal and type 'sh build.sh'. DO NOT use sudo. 4. The deb will show up in sdk/rifidi/debian/Debian-packages 5. Immediately move the deb out of the Debian-packages and install it via "sudo dpkg -i (deb)". Test it and make sure everything is correct. If you need to change anything, you'll probably need to hook up the SDK to SVN again (or delete and re-download it from SVN).
Server Only Zip
Prerequisites
1. You'll need a debian package you are satisfied is working correctly to make the zip.
Steps
1. Open the deb with an archive tool and extract the "rifidi" folder. 2. Zip up the folder to a 7zip file with the name "RifidiEdge-XXX-server_only.7z", where XXX is the version number, like "3.1.0".
Windows Installer
Prerequisites
1. You need to be on windows to make the windows installer. 2. You need the installer
Steps
SDK
Prerequisites
All you need is a workspace with the SDK
