Gonut reports that there is no staticfile_buildpack, but there is one listed.

# gonut push static --summary full
Skipping push of Staticfile sample app, because there is no staticfile_buildpack installed.
#
#
# cf buildpacks
Getting buildpacks...

buildpack                               position   enabled   locked   filename
liberty-for-java                        1          true      false    buildpack_liberty-for-java_v3.31-20190423-1354.zip
sdk-for-nodejs                          2          true      false    buildpack_sdk-for-nodejs_v3.26-20190313-1440.zip
dotnet-core                             3          true      false    buildpack_dotnet-core_v2.2-20190327-1013.zip
swift_buildpack                         4          true      false    buildpack_swift_v2.0.20-20190401-2122.zip
java_buildpack                          5          true      false    java-buildpack-v3.13.zip
ruby_buildpack                          6          true      false    ruby_buildpack-cached-v1.6.34.zip
nodejs_buildpack                        7          true      false    nodejs_buildpack-cached-v1.5.29.zip
go_buildpack                            8          true      false    go_buildpack-cached-v1.7.18.zip
python_buildpack                        9          true      false    python_buildpack-cached-v1.5.15.zip
php_buildpack                           10         true      false    php_buildpack-cached-v4.3.27.zip
xpages_buildpack                        11         true      false    xpages_buildpack_v1.2.6-20170331-1518.zip
staticfile_buildpack                    12         true      false    staticfile_buildpack-cached-v1.3.17.zip
binary_buildpack                        13         true      false    binary_buildpack-cached-v1.0.9.zip

@m-lukas FYI

Add delete/cleanup command to remove all apps that were pushed by gonut.

Dependabot can't resolve your Go dependency files.

As a result, Dependabot couldn't update your dependencies.

The error Dependabot encountered was:

fatal: The remote end hung up unexpectedly

If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.

View the update logs.

In case there is an error, e.g. not logged in, provide a well structured easy to read output of the error.

Add binary-buildpack compatible sample app to the list of sample apps.

Add a Ruby-based sample app to the list of sample apps.

During operations, in case of staging/hosting issues, we do additional steps to find which cell staged/hosted the gonut app. To overcome that, it is feasible to add the staging and the hosting cell information ( i.e. cell id)

Add NodeJS-based sample app to the list of sample apps.

Add command to easily update the current gonut version.

Check whether the pushed app is reachable and responds with 200 status code or not, the check could be either 1) a separated flag for the push command, or 2) a new summary type which includes such check.

Add .Net-based sample app to the list of sample apps.

Add some kind of output to the end of the push command to indicate that everything worked well. This message should be short.

It should be possible to disable this output by using a new --quiet flag.

Add an option to the summary flag called json to push command to enforce a computer readable output of the summary. Pre-req for this issue is #8.

Example:

gonut push static --summary json

The Java Sample Application, introduced with PR #75, due to the underlying JVM, requires around 572MB of memory. If the memory of the CF app is configurated in manifest.yml to be less than this value, it causes the following error and the application is timing out on start:

ERR Cannot calculate JVM memory configuration: There is insufficient memory remaining for heap. Memory available for allocation 128M is less than allocated memory 572292K (-XX:ReservedCodeCacheSize=240M, -XX:MaxDirectMemorySize=10M, -XX:MaxMetaspaceSize=60292K, -Xss1M * 250 threads)

However if started properly with sufficient memory, the app indeed uses less then 100MB.
The remaining memory is just reserved by the JVM.
This could possibly be fixed by tweaking the values of the error message in the start command.

Currently, if pushing with the 'all' option, it runs a loop through all sample applications and pushes each app successively. Also it doesn't merge the summaries (if turned on) of the pushed applications but rather shows them in a row in between the staging logs.
To allow better automation and to spead up this process, it might make sense to run the pushes as goroutines and combine the summaries to one.

Add Java-based sample app to the list of sample apps.

Before executing the CF push command, verify whether the respective buildpack is installed. Add a flag to manually override the check.

Recover panics from code at the command level and print a meaningful explanation that an unexpected error occurred.

With the introduction of the gonut logo and its colors, we should try to use the color style wherever possible. Suggestion: Update the version command to actually mimic the color and emphasis of the word gonut similar to how it is done in the logo.

Add new command called extract to download the sample app data to the local disk.

Add a summary flag that if set will print out a summary about the push statistics, e.g. create time, upload time, staging time, and starting time.

Add a flag to push the app not just to the default configured stack, but to another one or all of them depending on the setup.

Rough idea:

• do something similar to

  $ cf stacks
  Getting stacks in org system / space dev as admin...
  OK
  
  name         description
  cflinuxfs2   Cloud Foundry Linux-based filesystem
  

• run the cf push with flag -s <stack> to override the system default.

Add a flag called --asset to use a sample app that is not baked into gonut, but can be a URL (file://, http://, or Git repo location).

Example:
gonut push --asset https://github.com/IBM-Cloud/get-started-node

Alternatively, test whether the --asset flag can be omitted in case the command call itself is unique enough to be understood.
gonut push https://github.com/IBM-Cloud/get-started-node