Up to version 0.7.3, the :delete action in providers/application.rb neglects to remove the running application from memory. This causes future pm2 save/dump commands to write this to the dump file and then pm2 resurrect brings it back despite it being removed from the /etc/pm2/conf.d directory.
Need to add a pm2_command('delete') if pm2_app_online? after deleting the config file.
Alternatively, since pm2 delete stops it, you could replace the stop command with delete.
Up to version 0.7.3, the :delete action in providers/application.rb neglects to remove the running application from memory. This causes future pm2 save/dump commands to write this to the dump file and then pm2 resurrect brings it back despite it being removed from the /etc/pm2/conf.d directory.
Need to add a
pm2_command('delete') if pm2_app_online?after deleting the config file.Alternatively, since pm2 delete stops it, you could replace the stop command with delete.