Features

• worker: worker option to use dot env (#289) (ba3d312)

Bug Fixes

• appserver: use pumactl start for restart if the puma.state file does not exists (#276) (c2c8713), closes #274

Features

• worker: add good_job support (af98d67)

1.21.1 (2021-10-13)

Bug Fixes

• modify the restart process for puma so that it can do a proper restart instead of killing and restarting the app (#257) (035ffb9)

Bug Fixes

• patch broken SSL certificates list (4887cf5), closes #268
• update rubies for ruby-nq and fullstack, set default ruby to 2.7 (09ba7e1), closes #266

BREAKING CHANGES

• By default new list of SSL certificates is used.

It should not affect any of your current deployments, but if you start seeing SSL errors, the first thing you should check, is disabling node['patches']['chef12_ssl_fix'] option.

See #268 for more information.

Features

• webserver: apache2 - configurable mod_status (a82335d), closes #259

Bug Fixes

• run monit reload only once, after configure hook (1b784d1), closes #251

1.20.1 (2020-12-12)

Features

• webserver: add CORS for /packs endpoints (ede019d), closes #248

Bug Fixes

• setup: fix fullstaq key url (#247) (62ced10)

Features

• appserver: move appserver processes to foreground (37b9465), closes #244
• deploy: use revision-based deploy provider (#245) (27887e6)

BREAKING CHANGES

• appserver: Theoretically everything should work out of the box,
  and you shouldn't notice any change on your environment. However if your
  appserver start behave oddly (or probably - won't start at all) - this
  may be the first reason for that. Check generated monit files, check if
  monit is running and also check the syslog (monit is configured to write
  all the appserver output there).

Features

• deploy: include deploy resource polyfill (4f6d6fd), closes #242

Bug Fixes

• setup: link fullstaq ruby to /usr/local/bin (559c015), closes #237