It's not clear that node-foreman is providing much value added at this point. It's intended to replicate a Heroku-like multi-process environment, but most people running Spoke on Heroku use JOBS_SAME_PROCESS=1. Also, our Heroku deployment strategy is now container-based (thanks, @jlegrone!).
In the general interest of sloughing off dependencies and improving developer experience, we should determine whether we really need nf for anything, and get rid of it if not.
It's not clear that
node-foreman
is providing much value added at this point. It's intended to replicate a Heroku-like multi-process environment, but most people running Spoke on Heroku useJOBS_SAME_PROCESS=1
. Also, our Heroku deployment strategy is now container-based (thanks, @jlegrone!).In the general interest of sloughing off dependencies and improving developer experience, we should determine whether we really need
nf
for anything, and get rid of it if not.