Difference between revisions of "How to Package Rifidi Edge"
From RifidiWiki
(→Introduction) |
|||
| Line 2: | Line 2: | ||
These are the prerequisites and steps for packaing the Rifidi Edge SDK, Deb, Server Only Zip and Windows Installer | 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= | =Deb= | ||
==Prerequisites== | ==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. | ||
==Steps== | ==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. This is necessary to | ||
=Server Only Zip= | =Server Only Zip= | ||
==Prerequisites== | ==Prerequisites== | ||
| Line 13: | Line 24: | ||
=Windows Installer= | =Windows Installer= | ||
==Prerequisites== | ==Prerequisites== | ||
| + | ==Steps== | ||
| + | =SDK= | ||
| + | ==Prerequisites== | ||
| + | All you need is a workspace with the SDK | ||
==Steps== | ==Steps== | ||
Revision as of 03:08, 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.
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. This is necessary to
Server Only Zip
Prerequisites
Steps
Windows Installer
Prerequisites
Steps
SDK
Prerequisites
All you need is a workspace with the SDK
