Version 3.1.2
Periodic 3.1.2, Configuration and Memory Performance.
- Running with nodemon, removing PM2 requirement for production
- moving extension config to
content/config/extensions.json - moved restart.json to
content/config - added enterprise data security requirements for dbseed, custom data scrubbing
- added support for environemnt specific extensions for testing
- requires node >= 0.10.31, npm >= 2.0.0
Notes
Periodic Migration guide from 3.0.0
# move content/extensions/extensions.json, content/extensions/log, content/extensions/restart.json to content/config
# delete content/extensions directory
# install latest version of periodic
$ npm install forever -g # install forever
$ cd /path/to/web/app
$ npm install [email protected] --prefix ./ # or $ npm install periodicjs@latest
Periodic Runtime Options
$ npm start --e [name-of-environment (development by default)] # runs nodemon
$ npm run forever --e [name-of-environment (development by default)] # runs forever + nodemon
$ npm run deploy --e [name-of-environment (development by default)] # deploys with pm2
$ npm run sync # syncs dependencies
Running npm start saves the environment in content/config/process/runtime.json, if no environment is specified, it will reload in this environment, this is helpful server restarts