RU | EN

Push Sender Config

Description

The application installs the configuration file for Push Sender.
The project demonstrates creating packages to install files for other applications in your organization.

Build status:

1. example -
2. dev -

Table of Contents

• Compatibility
• Branch info
• Install and launch
• Project Structure
• Terms of Use and Participation in Development

Compatibility

The project is compatible with version 4.x.x of the Aurora OS.

Branch info

Application versions conform to the branch naming convention

Install and launch

Prepare for operation

The default path for config installation is /usr/share/common/en.auroraos/PushSender/configuration.yaml. The path for the config is set in the .spec file. If necessary, the path can be changed to /usr/share/common/en.auroraos/PushSendeConfig/configuration.yaml. The specific path is needed, for the PushSender application, to load the configuration file. A sample configuration file 'app_server_configuration_example.yaml' can be seen in the ./config directory.

Important

There are a few important aspects to consider when installing the package:

1. Before installing PushSenderConfig on the device (emulator) you should make sure that there is no already installed configuration .yaml file on the necessary path configuration .yaml file. If there is no such file, the package ru.auroraos.PushSenderConfig will be installed, if there is, go to step 2.
2. There are two options:
   • Choose a different path for the installation, if one is available. There can be three such paths: /usr/share/common/\${ORGNAME}, /usr/share/common/\${ORGNAME}/\${APPNAME}, /usr/share/common/\${ORGNAME}/\${CONFAPPNAME}.
   • Find the application with which the configuration file was installed. Only this application can update the configuration file.

Features

1. Aurora OS versions starting with 5.0.1.

   • Availability of Aurora Center on the device and its registration

2. Aurora OS versions up to 5.0.1.

   • Configuring push service - set address, port and set the flag for crlValidation to false. To get the current settings, you can use the command devel-su gdbus call -y -d ru.omprussia.PushDaemon -o /ru/omprussia/PushDaemon -m ru.omprussia.PushDaemon.GetNetworkConfiguration. To set the parameters: devel-su gdbus call -y -d ru.omprussia.PushDaemon -o /ru/omprussia/PushDaemon -m ru.omprussia.PushDaemon.SetNetworkConfiguration “{‘address’:<‘push-server.ru’>, 'port':<8000>,'crlValidation':<false>"} (it is important that the host be protocol-free, e.g. https://),
   • Restart push-daemon using the devel-su systemctl restart push-daemon command.

Features after installation

The application is not runnable and only installs the configuration file. To prevent the application from showing up in the application list, you must modify the .desktop file:

[Desktop Entry].
# ...
NoDisplay=true
# ...

Project Structure

The project has a standard structure of an application based on C++ and QML for Aurora OS.

Since the project uses only QML, the project contains only the configuration file and files, necessary for QML.

• ru.auroraos.PushSenderConfig.pro file describes the project structure for the qmake build system.
• config directory contains .yaml file configuration.
• icons directory contains application icons for different screen resolutions.
• qml directory contains the QML source code and the UI resources.
  • ru.auroraos.PushSenderConfig.qml file provides the application window implementation.
• rpm directory contains the rpm-package build settings.
  • ru.auroraos.PushSenderConfig.spec file is used by rpmbuild tool.
• ru.auroraos.PushSenderConfig.desktop file defines the display and parameters for launching the application.

Terms of Use and Participation in Development

The source code of the project is provided under license, which allows to use it in third-party applications.
The fonts used in the application are provided under license. It authorizes the use, modification, and distribution of the the font as part of the software or as part of the design.

To participate in the development of the project, please read the member agreement. If you plan to submit your own source code for inclusion in the project, you will need to accept the CLA terms and conditions.

Participant information is listed in the AUTHORS file.

The Code of Conduct is the current set of rules of the Open Mobile Platform Company, which informs about the expectations for interaction between community members when communicating and working on projects.