Which lab is it that you're having issues with?
Lab: Docker for Java Developers

Description

When deploying Java applications in production one usually specifies the amount of memory available to the JVM (-Xmx) and other assorted configuration settings. Unfortunately, this is (usually) static configuration and therefore fixed in the container image. When specifying memory constraints

The "Tag" section on each guide can encourage use of them for better asset management.
In this case (running labs) we can use them to mark resources created during the lab and tear them down later more quickly.

I would like to write the guide for the "isso" commenting platform.

It is powered by python and can be used to inject commenting functionalities to blogs or other static site generators. It works similar as commento.

If -Verbose is not enabled when installing a Lab, the Build process not reported to the user.

Should add Write-Information and Write-Progress to indicate progress of install.

https://github.com/apigee/apijam/blob/master/Labs/Appendix/API%20Development%20-%20Composite%20APIs/media/image_0.png

Note that two of the steps are specific to BaaS, for building a BaaS query, and should be replaced with a single step to add latitude and longitude query string parameters before calling target endpoint.

The second cat command is missing the apiVersion line.
Should be:

cat <<EOF | kubectl apply -f -
apiVersion: networking.istio.io/v1alpha3

Also, in the current version of Istio, we need to run:

kubectl apply -f samples/bookinfo/networking/virtual-service-all-v1.yaml -n default
kubectl apply -f samples/bookinfo/networking/destination-rule-all-mtls.yaml -n default

instead

When we search for files to render, we should recursively check the given directory. Currently we only search the given directory.

docs/
  components/
    a.md
    b.md
  overview/
    installation.md

Need to size VMs accordingly:

• Master - 4 gigs RAM, 1 cpu
• Nodes - 1 gig RAM, 1 cpu

Need to make sure hugepages is disabled on nodes.

There are very few but important posts on http://blog.datahub.io. All posts should live as their own "sticky" topics here: https://discuss.okfn.org/c/open-knowledge-labs/datahub/

See: okfn/okfn.github.com#389 (comment)