From 43b63e09e207fb3f07f5d27190a10df2e51aec1d Mon Sep 17 00:00:00 2001 From: "Kent C. Dodds" Date: Thu, 24 Mar 2022 09:15:28 -0600 Subject: [PATCH] add note about fly community --- README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/README.md b/README.md index 491147b1..d7e62832 100644 --- a/README.md +++ b/README.md @@ -110,6 +110,8 @@ Prior to your first deployment, you'll need to do a few things: Now that every is set up you can commit and push your changes to your repo. Every commit to your `main` branch will trigger a deployment to your production environment, and every commit to your `dev` branch will trigger a deployment to your staging environment. +If you run into any issues deploying to Fly, make sure you've followed all of the steps above and if you have, then post as many details about your deployment (including your app name) to [the Fly support community](https://community.fly.io). They're normally pretty responsive over there and hopefully can help resolve any of your deployment issues and questions. + ## GitHub Actions We use GitHub Actions for continuous integration and deployment. Anything that gets into the `main` branch will be deployed to production after running tests/build/etc. Anything in the `dev` branch will be deployed to staging.