Documentation Index
Fetch the complete documentation index at: https://docs.neuro-tech.io/llms.txt
Use this file to discover all available pages before exploring further.
Building packages
There are two types of packages:- Content only — contain content files like Markdown, scripts, and JavaScript
- Assembly packages — can install C# assembly files, extending Neuron capabilities
Prerequisites
To create a package file you need:- All package contents in a folder (a content folder or a Dotnet project output folder)
- A
.manifestfile describing all package content — only listed files are shipped - Encryption keys to encrypt and sign the package
Waher.Utility.InstallandWaher.Utility.Sign— available by installing the Neuron or building from the IoTGateway repo
Steps
- Write the package code to a functional state
- Generate the
.packagefile - Sign the
.packagefile, generating a.signaturefile
Waher.Utility.Install or the Neuron admin dashboard.
Generating the necessary keys
We recommend Ed448 for signatures and AES-256 for encryption. If you have access to a Neuron, use this script in the script console:Generating the .package file
UseWaher.Utility.Install.exe with these flags:
-p PACKAGE_NAME.package-k AES_KEY-m MANIFEST_FILE
Waher.Utility.Install at C:\Program Files (x86)\Neuron\InstallUtility.
After running this command you will have a PACKAGE_NAME.package file in the active folder.
Signing the package
To generate the.signature file, use Waher.Utility.Sign.exe with these flags:
-c ed448-priv PRIVATE_KEY-o PACKAGE_NAME.signature-s PACKAGE_NAME.package
Waher.Utility.Sign at C:\Program Files (x86)\Neuron if installed via the installer.
After this you are ready to distribute the package.