anchor.diff:  generated: the `blobs.yml` file and the `dev.yml` file.
   
   Adapt the examples below to fit the specifics of your release.
  +Our example release uses the `local` type blobstore because otherwise it would
  +be necessary to explain how to configure a public blobstore such as
  +Amazon S3, which is too large a topic for this context.
  +
  +The `local` type blobstore is suitable for learning but the resulting release
  +cannot be shared.
  +For that reason, you should configure a non-local, publicly available blobstore
  +for releases that you intend to share.
  +Normally, the blobstore you choose when you begin working on a release is used
  +for all subsequent versions of the release.
  +Changing the blobstore that a release uses is beyond the scope of this tutorial.
   
   Example `final.yml`:
   
  
positive.code: VM creation in BOSH works on consistent principles that are important to know
  when you debug a release:
  
  * Compilation VMs are newly created every time you deploy.
  
  * Job VMs are newly created in two cases: the first time you deploy a release,
  and every time that you deploy using the `--recreate` option.
  
  ### <a id="what"></a> Decide What to Release ###
  
negative.code: content does not matter.
  There is never `blobstore_secret` line for blobstores of types other than
  `local`.
  
  ### <a id="inform"></a> Inform BOSH where blobs are ###
  
  