Releases: Unitech/pm2
Releases · Unitech/pm2
Release list
v0.14.1
v0.14.0 CrystalClear (Current stable)
��- Removed: pm2.startJSON() method, now call pm2.start()
- API Change: pm2 start <app_name|app_id> restart an application already launched
- API Change: pm2 start restart all json apps if already launched
- pm2 start all - restart all applications
- pm2 reload <json_file> possible
- pm2 gracefulReload <json_file> possible
- Smart start (pm2 start app.js ; pm2 stop app ; pm2 start app)
- Reduced memory footprint
- Reduced pipelined data
- Reduced CPU usage
- Faster command processing
- Upgrade shelljs, semver, colors, chalk, coffee-script, async, json-stringify-safe, cron, debug, commander
- Fix: launchBus() only connects and disconnects once
- Refactored
pm2 logs:- Now you don't need to install tail on Windows
- You don't need to Ctrl^C and
pm2 logsagain when a new app is launched (this one will be detected and added to the real-time logs output) - Logs are shown in chronological order at a file level (modified date)
- More verbosity : tailed logs are explicitely separated from the real-time logs
- Real-time logs now use the
busevent emitter - PM2 logs added to the
bus --lines <n>and--rawflags available forpm2 logscommand- New flag : '--timestamp [format]' // default format is 'YYYY-MM-DD-HH:mm:ss'
- Now you can exclusively show PM2 logs by doing
pm2 logs PM2
v0.12.16
- Feature : File transmission added in Agent
- Feature : Transmit Node.js/io.js version in Agent
- Feature : Parameters can be passed to remote actions
- Feature : Support JS in addition to JSON and JSON5 config files #1298
- Enhanced: pm2 conf display all configuration values
- Enhanced: pm2-dev
- Enhanced: Better error messages when validating data passed via CLI
- Enhanced: Smaller memory footprint for PM2 (~30%)
- Fix #1285 : PID file was deleted after a reload/gracefulReload
- Fix : ENOMEM made PM2 crash
v0.12.15
- Fix #941 : Env variables overriden when an app is restarted
- max_memory_restart now performs a graceful reload
pm2 logs --rawnow shows 20 last lines of each log file- pm2-dev run app.js : start an app in dev mode (--no-daemon --watch and stream logs of all launched apps)
- --no-daemon command now display logs of all processes (Docker)
v0.12.14
v0.12.13
- Enhanced : PM2 doesn't leave processes behind when it crashes
- Enhanced : Call reload instead of restart when max-memory-limit reached
- Enhanced : Modules are compatible ES6 by default by adding --harmony flag
- Enhanced : Dump feature is now smarter
- Fix #1206 : fix
pm2 logsbug when merged_logs - Fix : pm2 scale doesn't try to scale a fork_mode process
0.12.12
- New command: pm2 scale - scale up/down an application
- Added: Using Keymetrics harden PM2 by enabling a WatchDog that auto restart PM2 in case of crash
- pm2 logs --raw flag : show logs in raw format
- Fix #1177 : now concurrent vizion.parse() for the same process event when it restarts
- Added: Expose kill method programmatically
- Added: Call disconnect without a function
- Added: Programmatic call to .connect can now take no-daemon-option
- Fixed: starting a JSON programmatically return a process list coming from God
- Fixed: Reflect dump functions from CLI and God
- Enhanced: New CLI API for configuring modules (pm2 conf module.option [value])
- Added: Expose pm2 gc programmatically
- Added: pm2 install update the module
- Enhanced: 4 new test suites for PM2 programmatic calls
- Enhanced: Documentation restructured
0.12.11
We strongly recommend you to always update your PM2 since it comes more stable and efficient at every release.
- Enhancement: Reduced memory footprint !
--no-autorestartflag : starts an app without automatic restart feature
("autorestart" : falsein JSON declaration)--no-vizionflag : starts an app completely without vizion features
("vizion" : falsein JSON declaration)- Fix #1146 : add module._initPaths() on ProcessContainer.js so it forces each
new process to take the current NODE_PATH env value in account - New: pm2.start() now handles json objects as param
- Added: timestamps to KM agent logs
- Fix: now properly closes all fds after logging has finished.
- New command: pm2 gc (manually triggers garbage collection for PM2)
- VersioningManagment: exec() timeout configurable via .json
- Fix #1143 :
If we start let's say 4 instances of an app (cluster_mode),
Each app will have a value in process.env.NODE_APP_INSTANCE which will be 0 for the first one,
1, 2 and 3 for the next ones. - Fix #1154 :
Negative arguments to '-i' are substracted to CPU cores number.
E.g: 'pm2 start app.js -i -3' in a 8 cpus environment will start 5 instances (8 - 3).
0.12.10
- Fix : PM2 interactor doesn't send data about dead processes ('old') anymore.
- Fix #1137 : Safe params for 'pm2 list' so cli-table won't fail
- Refactored reverse interaction with keymetrics for better stability and more verbosity on Rollback/Pull/Upgrade operations
0.12.9
- Fix #1124 : PM2_PROGRAMMATIC flag wasn't handled properly
- Fix #1121 : NODE_PATH before PATH so custom node versions come first
- Fix #1119 : Safe params so cli-table won't fail
- Fix #1099 : Bug when app name starts by digit (e.g '1-myApp')
- Fix #1111 : More verbosity on writeFileSync errors
- New env setting: PM2_KILL_TIMEOUT (ms) : time to wait before a process is considered dead
- New env setting: PM2_CONCURRENT_ACTIONS : use it with care, value bigger than 1 is considered unstable
- Refactored reload/gracefulReload for better stability