dapp-installer, folder and file naming should comply with
service module naming conventions.
product id(uuid v4). We expect in future to create mapping between service module maintainer ethereum address and unique product id. This will give ability for a maintainer to reserve
product idfor his service module and sign his service module. User/software will have ability to:
product id's) as trusted maintainer
bin- contains all binary/executable/scripts. Can contain subfolders. Can contain 3rd party software in subfolders. During upgrade, it should be replaced by newer versions.
config- adapter config and preferably all other config files. During upgrade, it should be left with or without changes of config files.
data- folder to store any data. It remains during upgrade.
log- log of adapter. Preferably any other logs goes here.
template- offering, access, product template stored here and imported during install of service module.
templatefolder. Following naming and folder structure must be maintained:
client.json- client product object that imported to Privatix Core DB to products table. Represents client service module initial configuration/settings.
server.json- server product object that imported to Privatix Core DB to products table. Represents server service module initial configuration/settings.
adapter.agent.config.json- service module adapter configuration file for Agent. It is template only for customization during installation. Resulting config file should reside in
adapter.client.config.json- service module adapter configuration file for Client. It is template only for customization during installation. Resulting config file should reside in
configfolder by dapp-installer, they would be executed sequentially as part of install, update or remove workflow.
Adminfield specifies, if command will be executed with admin/root privileges.