A package management system for node.
WARNING: Eve is in development and has not passed testing. DO NOT USE IN LIVE ENVIRONMENTS!
$ npm install -g eve-pms
1 - Update
$ sudo eve environments
2 - Install
$ eve create
3 - Point Apache to deploy/admin
4 - Point Apache to deploy/web
5 - Install server dependencies
$ cd deploy/server
$ npm install
6 - Watch the folder
Mainly used to address a problem we had at Openovate Labs. I needed a library to address end-to-end package reusage. Why build the same register/login form over and over for different projects ? Why do admin interfaces need to look different from each other ? Why does testing need to change across projects ? (Not the actual test files...)
Packages in Eve are different from npm packages. Packages in Eve are more like mini apps in your project that surround a particular object like a post. A post package in Eve is plug and play with the REST, admin and general front end usage pre built in. Packages in Eve should be developed as independant from each other as best as possible.
eve generate post
[YOUR ADMIN URL]/post
eve generate post_user
eve generate post
[YOUR ADMIN URL]/post/update/1you should see a tab called Users
eve - Alias for "eve watch all"eve database - Adds a database to build.jsoneve remove [name] - removes package from deployseve map - updates all mapseve create - Alias for "eve install all"eve create/web [name] - Installs web onlyeve create/admin [name] - Installs admin onlyeve create/server [name] - Installs server onlyeve deploy - deploys entire build to deploy folderseve watch - Alias for "eve watch all"eve watch [name] - Watches changes in [name] onlyeve generate [name] - Generates a package given the schema.json in that same foldereve relate [name] - Generates a relational package given the schema.json in that same folder