layout | |||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Fly is fantastic. Super happy to be on it.
These are the rough edges we've bumped up against, and (when applicable) how we handle it.
- auto-stop doesn't seeeeeem to work properly when websockets are in the mix
- restart
- doesn't support
--process-group
- workaround (including backgrounding each Machine's individual restart command):
fly m list -a $APP | grep $PROCESS_GROUP | awk NF | awk '{ print "fly m restart " $1 " &;" }'
- workaround (including backgrounding each Machine's individual restart command):
- slow for restarting large numbers of Machines, and halts if any individual restart fails
- workaround: use
fly m restart $ID &
instead - addressed in Restarting apps
- workaround: use
- doesn't support
- status
- no machine-readable output; we regex our way through it to get Machine status
- nb:
--display-config
exists, but that's for something else
- nb:
- doesn't include healthchecks
fly checks list -a $app | grep $machine_id
- no machine-readable output; we regex our way through it to get Machine status
- count
- it seems to grab a lease on all Machines at once, even when scoped by
--process-group
, which meansfly scale count
commands can't be run concurrently- no workaround
- it seems to grab a lease on all Machines at once, even when scoped by