In order for Momotor to use these packages, they must be converted into recipes by adding a recipe.xml file to the package. This recipe instructs Momotor to execute each step configured in the package's Python file using the checklet that emulates daemon2.
The recipe.xml for a daemon2 package can be automatically generated by parsing the package's Python file. Upload the package using the form on this page and click on 'submit'. The recipe.xml will be generated and download automatically. The generated recipe.xml should be added to (the root of) the package zip file to create the complete Momotor recipe. Do not change the name of the file, Momotor will only accept recipes containg a file named recipe.xml in the root of the zip file. No other modifications to the package are necessary. In contrast to daemon2, the name of the zip-file itself is irrelevant.
Note: The generated recipe.xml contains signatures of files referenced from the Python script inside the package and Momotor will validate these signatures. If you change any file inside the package, the recipe.xml must be regenerated.
Besides a recipe, Momotor also needs a configuration file. For converted packages, these simply contain the programming language to expect. Download the appropriate configuration file from the table below. Use right-click and 'save as...' to save the file instead of opening it:
|Programming Language||Configuration file|
|C||config_c.xml (308 bytes)|
|C99||config_c99.xml (310 bytes)|
|C++||config_cpp.xml (310 bytes)|
|CIF 3||config_cif3.xml (311 bytes)|
|Java (highest available version *)||config_java.xml (311 bytes)|
|Java 7||config_java7.xml (312 bytes)|
|Java 8||config_java8.xml (312 bytes)|
|Java 9||config_java9.xml (312 bytes)|
*) "Highest available Java version" configuration will use Java 8 before November 6th, 2017 and Java 9 after