===========================================================
                                      .___ __  __   
          _________________  __ __  __| _/|__|/  |_ 
         / ___\_` __ \__  \ |  |  \/ __ | | \\_  __\
        / /_/  >  | \// __ \|  |  / /_/ | |  ||  |  
        \___  /|__|  (____  /____/\____ | |__||__|  
       /_____/            \/           \/           
              grep rough audit - static analysis tool
                  v2.8 written by @Wireghoul
=================================[justanotherhacker.com]===
bundlewrap-4.2.2/docs/content/guide/env.md-38-
bundlewrap-4.2.2/docs/content/guide/env.md:39:When BundleWrap [locks](locks.md) a node, it stores a short description about "you". By default, this is the string `$USER@$HOSTNAME`, e.g. `john@mymachine`. You can use `BW_IDENTITY` to specify a custom string. (No variables will be evaluated in user supplied strings.)
bundlewrap-4.2.2/docs/content/guide/env.md-40-
##############################################
bundlewrap-4.2.2/docs/content/guide/item_file_templates.md-12-
bundlewrap-4.2.2/docs/content/guide/item_file_templates.md:13:As you can see, `${...}` can be used to insert the value of a context variable into the rendered file. By default, you have access to two variables in every template: `node` and `repo`. They are `bundlewrap.node.Node` and `bundlewrap.repo.Repository` objects, respectively. You can learn more about the attributes and methods of these objects in the [API docs](api.md), but here are a few examples:
bundlewrap-4.2.2/docs/content/guide/item_file_templates.md-14-
##############################################
bundlewrap-4.2.2/docs/content/guide/secrets.md-109-
bundlewrap-4.2.2/docs/content/guide/secrets.md:110:The encrypted data will be prefixed by `yourkeyname$...` to indicate that the key `yourkeyname` was used for encryption. Thus, during decryption, you can omit the `key=` parameter.
bundlewrap-4.2.2/docs/content/guide/secrets.md-111-