The purpose of this document is to teach you how to package an application for YunoHost.
To package an application, here are the requirements:
* An account on a git server (e.g. GitHub) to publish the application;
* Basic knowledge of
git, bash shell and other programming stuff;
* A testing virtual machine or a distant server, or a development environement, ynh-dev or VirtualBox, to package and test the package.
A YunoHost package is composed of:
scriptsdirectory, which contains five Shell scripts:
- Optional directories, containing
LICENSEfile containing the license of the package
- A presentation page of your package in a
A basic package feel free to use it as a framework.
Architecture and arguments
Since YunoHost has a unified architecture, you will be able to guess most of the settings you need. But if you need variable ones, like the domain or web path, you will have to ask the administrator at installation (see
arguments section in the manifest above).
YunoHost provides a hook system, which is accessible via the packager's script callbacks in moulinette (CLI).
The scripts have to be placed in the
hooks repository at the root of the YunoHost package, and must be named
priority-hook_name, for example:
hooks/50-post_user_create will be executed after each user creation.
priority is optional, default is
Take a look at the ownCloud package for a working example.
In order to test your package, you can execute your script standalone as
admin (do not forget to append required arguments):
su - admin -c "/bin/bash /path/to/my/script my_arg1 my_arg2"
Or you can use moulinette:
yunohost app install /path/to/my/app/package
Note that it also works with a Git URL:
yunohost app install https://github.com/author/my_app_package.git
Packaging best practices
Here is a list of best practices for application install scripts:
* scripts should use
sudo cp -a ../sources/. $final_path instead of
sudo cp -a ../sources/* $final_path;
* install script must contain support in case of script errors to delete residuals files thanks to
set -e and trap;
* install script should use the command-line method instead of calls to curl through web install form;
* install script should save install answers;
* application sources should be checked with a control sum (sha256, sha1 or md5) or a PGP signature;
* scripts should be tested on Debian Jessie as well as 32 bits, 64 bits and ARM architectures;
* backup and restore scripts should be present and functional.
Package script checker
This Python script checks: * that the package is up to date wich last specifications * that all files are present * that the manifest doesn't have syntax errors * that scripts exit well before modifing the system during verification.
Publish and ask for testing your application
Subscribe to the Apps mailing list to be informed about packaging evolution.
Officalization of an application
To become an official application, it must be tested well enough, be stable and should work on 64 bits, 32 bits et ARM processor architectures, and on Debian Jessie. If you think those conditions are met, ask for official integration of your application.