- Technical documentation
- API docs
Unlike the other application types the native (Debian) applications do not run in sandboxes. Instead, they run directly on the host machine. The application package is presumed to contain Debian packages or have Debian package repositories defined in the applications manifest (apt_packages, apt_repositories, deb_packages). Hence the Debian definition in the application type.
- The lifecycle of a native_debian application is managed using systemd.
- Each native_debian application must define and install (using standard debian mechanisms) a systemd service with the service name constructed of applications unique_name followed by the .service extension. The unique_name field of spaceify.manifest allows forward slash and underscore characters. These characters must be removed from the final service name for it to be a valid service name in the Spaceify ecosystem, e.g. spaceify/events would become spaceifyevents.service. The service file must be in the application directory of the Spaceify package.
The installation proceeds similarly to other application types. After the installation the files in the package can be found from their directory. The files provide edge enough information for Spaceify to handle the native application. However, the nature of native applications makes it hard for Spaceify to control them in such fine-tuned precision as the other application types. For example native applications must allocate TCP/IP ports themselves and register their services with the port information.