Deployment guide (and more)

[aoberoi]

(Update) We've started releasing a few deployment guides:

• Heroku ⚡️ Bolt for JavaScript (released 2020-10-07)
  • Guide
  • Pull request
• AWS Lambda ⚡️ Bolt for JavaScript (released 2020-12-10)
  • Guide
  • Pull request
• Container platform
  • Please leave comments on what guide you'd like next!

---

Description

Produce a documentation guide which describes the process of deploying a Bolt app to various hosting platforms. This is a list of possible hosting providers, in roughly priority order:

1. AWS Lambda (most requests to date)
2. Heroku (easiest) - Deploy to Heroku button
3. Docker (most wide reach)
4. Azure (Functions, Web App, etc)
5. Google Cloud Platform (Firebase, Functions, Cloud Run, etc)
6. AWS (other services)
7. Zeit Now
8. Cloud Foundry
9. Codesandbox.io

Currently, we believe providers 1 through 4 are substantial enough for the first iteration of this guide.

We are looking for comments regarding:

• Which hosting platforms are important to you, or do you think should be prioritized sooner?

• Do you have any experience with the specific hosting providers mentioned, and can you advise on strategies you would recommend for the deployment to those providers?

Related work:

General:

• Do we need a custom receiver for any of these deployment targets?
• In serverless environments, how can we preserve the benefits of deploying small functions (independent scaling, cold boot time, etc)? Can we solve this by integrating Bolt with a message queue or similar technology offered by the serverless platform?
• Where should the templatized apps live? How do we reduce code duplication amongst them? AWS Quickstarts seem to all live in the same Org and have a contributors guide. Azure ARMs also seem to live in the same repo, which contains their contributing guide. Should the external repos just contain scripts which clone the one sample code repo?

AWS:

• How can we continue processing a request after the response is ended in Lambda?
• Cloud Formation templates for coordination between AWS services such as Lambda, API Gateway, data storage, etc.
• AWS Quickstarts
• AWS Serverless Application Repository

Heroku:

• "Deploy to Heroku" button, app.json
• Listing on https://elements.heroku.com/ marketplace

Docker:

• docker-compose.yml and Dockerfile
• Host an image on hub.docker.com

Azure:

• Azure Resource Manager (azuredeploy.json) template(s), "Deploy to Azure" button
• ARM template marketplace: https://azure.microsoft.com/en-us/resources/templates/

Requirements (place an x in each of the [ ])

• I've read and understood the Contributing guidelines and have done my best effort to follow them.
• I've read and agree to the Code of Conduct.
• I've searched for any related issues and avoided creating a duplicate issue.

[Startouf]

Hello, I have opened an issue regarding health checks of the application, it's related to cloud deployment #283

As far as I am concerned, I was just about to finish a state of the art infra-as-code deployment on AWS ECS (container), but then got stuck at the very end as I realised my service would keep rebooting because it failed the default health check, and I had no way to implement one

[seratch]

Quick update for the container service support: We've published a simple example app demonstrating how to build a Docker image for Bolt JS apps. https://github.com/slackapi/bolt-examples-aws-re-invent-2020/tree/main/lightsail-containers/javascript

Although we don't have guide document on the website yet, the steps to build a Docker image is the same for other platform services.

[mwbrooks]

Closing this since we have a Heroku and Lambda guide available. We also have an examples/ directory where we can continue to add more hosting examples as people request them.

We may want to import our AWS guides from https://github.com/slackapi/bolt-examples-aws-re-invent-2020 to showcase AWS Gateway Lambda and Lightsail