docs: Adds notes on Hermes packaging requirements

[saibatizoku]

Description

Adds documentation requirements for packaging Hermes Applications.

Related Issue(s)

List the issue numbers related to this pull request.

#70

Description of Changes

See the generated docs here.

• Overview
• Packaging A Hermes Application
• Defining Application Metadata
• Static Assets
• Application Data
• Application WASM Modules
• Application Signatures

Please confirm the following checks

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream module

[Mr-Leshiy]

Looks awesome !

But I have a question about private and public data, maybe it make sense to rename directories to the var/public and var/private instead of var/data, var/www ?
So it will make it more clear and from the packaging perspective we will don't care what exact data should be there, we are just managing the scope to it.

cc @stevenj

[saibatizoku]

Looks awesome !

But I have a question about private and public data, maybe it make sense to rename directories to the var/public and var/private instead of var/data, var/www ? So it will make it more clear and from the packaging perspective we will don't care what exact data should be there, we are just managing the scope to it.

cc @stevenj

Thanks! I'm open to renaming the paths, and I considered a similar approach to what you are proposing, but I think that public and private are terms that could lead to confusion, as they have different meanings depending on the context.

In this case, the context is using HDF5 files as a file-system, so using /var/data and /var/www, is similar to the convention in POSIX-based file-systems that should be familiar to most developers.

So, in this case, I would opt for keeping the names as they are, or to find a middle ground.

[FelipeRosa]

LGTM

[bkioshn]

Looks good, the document is clear and understandable 🥳