tappack 0.0.1

A packager for Tasmota Berry Application (TAPP) apps

tappack: Tasmota Application Packager

This tool aims to simplify packaging Tasmota Berry code as a TAPP file, including basic dependency resolution. It can be run locally, but is primarily intended for use during a release workflow, e.g. GitHub Actions.

What Does It Do?

It performs the following:

• Reads your project manifest file (see below), with a list of dependency URLs (other .tapp files).
• Downloads each, extracts and merges them, in a subfolder, it into your own code.
• Auto-generates an autoexec.be for your library that sets up all the relevant dependency paths.
• Packages the whole structure into a .tapp file ready for deployment.

Manifest File

Your project needs to contain a tappack manifest file, tappack.yaml, with at least fields name and dependencies. The latter is a mapping of module names to URLs of corresponding .tapp file. For example:

name: my_library
dependencies:
  tools: https://github.com/fmtr/tools/releases/download/v0.0.1/tools.tapp
  hct: https://github.com/fmtr/hct/releases/download/v0.3.27/hct.tapp

Example Usage

$tappack --module-path ./my_library --tapp-path ./my_library.tapp

Here --module-path should contain your Berry and manifest files.

No autoexec.be

Your module should not contain an autoexec.be, as tappack will generate one. If you need to run any code in the autoexec context, then ensure your module implements an autoexec method, which will be called once it is imported. For example:

var mod = module("my_module")

def autoexec()

    # Do autoexec stuff here.

end

mod.autoexec=autoexec
return mod