Conventions used

There are a number of text conventions used throughout this book.

Code in text: Indicates code words in text, database table names, folder names, filenames, file extensions, pathnames, dummy URLs, user input, and Twitter handles. Here is an example: “The /whisk.system namespace is reserved for entities that are distributed with the OpenWhisk system.”

A block of code is set as follows:

root@serverless101:~/hello-worker# cat index.js
addEventListener('fetch', event => {
  event.respondWith(handleRequest(event.request))
})
/**
 * Respond with hello worker text
 * @param {Request} request
 */
async function handleRequest(request) {
  return new Response('Hello worker!', {
    headers: { 'content-type': 'text/plain' },
  })
}

When we wish to draw your attention to a particular part of a code block, the relevant lines or items are set in bold:

root@serverless101:~/hello-worker# wrangler dev -i 0.0.0.0
Listening on http://0.0.0.0:8787
watching "./"

Any command-line input or output is written as follows:

aws cloudformation create-stack \
 --stack-name MyS3Bucket \
 --template-body file://tmp/cfntemplates/mys3.yml

Bold: Indicates a new term, an important word, or words that you see onscreen. For instance, words in menus or dialog boxes appear in bold. Here is an example: “The Kubernetes hairpin-mode shouldn’t be none as OpenWhisk endpoints should be able to loop back to themselves.”

Tips or important notes

Appear like this.