bundled server throw storage_temp's bundle tool error

[letsautom8]

After using gencert and docker-compose, the container throws an error on missing bundle tool

storage-temp_1          | runcli.js storage-temp
storage-temp_1          | 
storage-temp_1          | Options:
storage-temp_1          |   -h, --help         Show help.                                        [boolean]
storage-temp_1          |   -V, --version      Show version.                                     [boolean]
storage-temp_1          |   --max-file-size    Maximum file size to allow for uploads. Note that nginx may
storage-temp_1          |                      have a separate limit, meaning you should change both.
storage-temp_1          |                                                   [number] [default: 1073741824]
storage-temp_1          |   --port, -p         The port to bind to.               [number] [default: 7100]
storage-temp_1          |   --save-dir         The location where files are saved to.
storage-temp_1          |                                                       [string] [default: "/tmp"]
storage-temp_1          |   --bundletool-path  The path to bundletool binary.
storage-temp_1          |                             [string] [default: "/app/bundletool/bundletool.jar"]
storage-temp_1          |   --ks               The name of the keystore to sign APKs built from AAB.
storage-temp_1          |                                                    [string] [default: "openstf"]
storage-temp_1          |   --ks-key-alias     Indicates the alias to be used in the future to refer to
storage-temp_1          |                      the keystore.                   [string] [default: "mykey"]
storage-temp_1          |   --ks-pass          The password of the keystore. [string] [default: "openstf"]
storage-temp_1          |   --ks-key-pass      The password of the private key contained in keystore.
storage-temp_1          |                                                    [string] [default: "openstf"]
storage-temp_1          |   --ks-keyalg        The algorithm that is used to generate the key.
storage-temp_1          |                                                        [string] [default: "RSA"]
storage-temp_1          |   --ks-validity      Number of days of keystore validity.
storage-temp_1          |                                                         [number] [default: "90"]
storage-temp_1          |   --ks-keysize       Key size of the keystore.        [number] [default: "2048"]
storage-temp_1          |   --ks-dname         Keystore Distinguished Name, contain Common Name(CN),
storage-temp_1          |                      Organizational Unit (OU), Oranization(O), Locality (L),
storage-temp_1          |                      State (S) and Country (C).
storage-temp_1          |            [string] [default: "CN=openstf.io, OU=openstf, O=openstf, L=PaloAlto,
storage-temp_1          |                                                             S=California, C=US"]
storage-temp_1          | 
storage-temp_1          | Each option can be be overwritten with an environment variable by converting the
storage-temp_1          | option to uppercase, replacing dashes with underscores and prefixing it with
storage-temp_1          | `STF_STORAGE_TEMP_` (e.g. `STF_STORAGE_TEMP_SAVE_DIR`).
storage-temp_1          | 
storage-temp_1          | Cannot find module '../../util/bundletool'```

[issue-label-bot]

Issue-Label Bot is automatically applying the label bug to this issue, with a confidence of 0.86. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

[nanoscopic]

The bundletool stuff is some junk added by a third party contributor to upstream STF. I updated the PR fork of STF to contain updates for this, but it hasn't gone to master yet. It likely won't until someone spends the time to finish my PR: DeviceFarmer/stf#118

Also, I consider this an issue with upstream STF; you should open a ticket with that project here: https://github.com/devicefarmer/stf

Due to #82 I'm not sure when/if/ever this will be resolved.

Due to upstream STF never tagging their releases, you can't directly/easily use upstream without their new commits, you are always stuck with latest or an outdated version...

Essentially: upstream STF problem. This repo is not the right place to address it.

[nanoscopic]

It occurs to me that all new users of this repo will likely hit this problem if attempting to use the provided server/ config files. I will add documentation and/or some changes to make an easy way to work around this issue.