* Create serverless-deployment.md
I have worked alongside @tcbyrd and @JasonEtco testing out their Serverless plugins in preparation for a Serverless conference I am attending this week. Having a Serverless section would be nice to share while at the conference, but not required.
This PR adds a new Serverless section to the docs (open to suggestions on placement), @hiimbex mentioned creating a new section to assist not over-crowding the (already existing) deployment.md.
After this week, I plan to begin working with another provider (Azure).
* Update deployment.md
* Bdougie pr serverless fixes (#2)
* adds link to serverless docs
* link to deployments section for repeated content
* Bdougie pr serverless fixes (#3)
* adds link to serverless docs
* link to deployments section for repeated content
* Update serverless-deployment.md
* adds serverless blurb
* Update deployment.md
* Update serverless-deployment.md
* Update deployment.md
* Update serverless-deployment.md
* a few grammar and word changes
* Add env var INSTALLATION_TOKEN_TTL
* Fixed jest tests not running under yarn with insecure localhost warning
* Update configuration.md
* Added integration nock tests for Application auth cache
* Fix test comment typo
* Clean global variables both before and after auth cache tests
Stop using the names 'plugin' and 'app' to refer to instances of
ApplicationFunction.
This renames all variable names, but leaves the plugins folder in place,
to be renamed later
Both `get` and `set` are async in the metadata library. The `await` in `get` is required in this case because otherwise it will always to set a promise on the metadata, which doesn't make sense, and the await in set is required to not swallow the rejection if it fails.
This helps enforce the idea that a payload fixture file should be the
webhook payload body, so that the fixture can be referenced by both
tests and `probot simulate`.
* add env config docs
* fix environmental, add quotes
* actually commit all the things
* add npm rules blurb
* dotenv npm wording
* make formatting into a beautiful table
* place ordering before deployment
* fix md tables for gh markdown even though they work in atom readme preview
* specify defaults and add period
This replaces all internal references to "robot" with "app" or
"Application". There should be no functional change in public APIs, but
may cause some issues for anyone using internal APIs.
Shelley Vohr