General questions

2

Hi! I’m glad it’s working out for you, hopefully it continues!

  1. By default, we do a canary deploy. We spin up a new VM and make sure it’s healthy before we remove the old ones. You can control this with the --strategy flag on the deploy command, rolling to skip the canary and immediate to abruptly replace everything.
  2. Right, soft_limit controls how many instances will run. You probably don’t want balanced, though, that’s only appropriate for some apps. standard will add and remove in the regions you’ve specified.
  3. Yes, the health checks determine whether traffic gets routed to the VM or not. They have to start passing before they’ll receive requests.
  4. The build is just a remote Docker daemon, so .dockerignore is the right way to prevent files from being sent to the builder.