Another version of the legendary movie database. This time with NodeJS. The app is being deployed to Heroku after every push. Feel free to check it out: http://agilejs-team-4.herokuapp.com/!
More documentation is available through http://codecentric.github.io/movie-database-node.
This project uses Travis-CI for continuous integration. After every successfull build, the application is deployed automatically to Heroku.
If you fork the project, you probably want to set up a CI/CD-pipeline yourself. For Travis-CI, follow these steps (or take a look at the guide Travis-CI Getting started guide). If you are interested in the travis-configuration, take a look at the documented .travis.yml.
- Fork the project on GitHub.
- Create a Travis-CI account (you can login with your GitHub account).
- Activate the Travis service hook for your fork of the project (on your profile page).
- Change the build-status icon in this README.md file to the new travis project (https://travis-ci.org/YOUR_GITHUB_NAME/movie-database-node).
Deployment on Heroku is also easy. Just follow the Getting started with Heroku and NodeJS guide.
If you want your application to be deployed continuously, whenever a Travis-CI job succeeds, you have to encrypt your Heroku API Key and save it in the .travis.yml according to the Travis CI documentation:
Make sure that you have node.js with NPM installed on
your machine. You also need a Neo4j instance listening
on http://127.0.0.1:7474.
This project uses a standard node.js module descriptor (package.json) and
Grunt as a tool for test execution and static source
code analysis. To install the project's dependencies, simply run npm install
in the project's root directory. This will make sure that the development tools
are locally installed.
To make use of Grunt, you further need to have its CLI tool on your path.
npm install -g grunt-cli
The most useful Grunt tasks currently is test for test execution and
dev to run a development mode. To execute these tasks, simple call
Grunt:
grunt dev
The development mode will automatically spin up a server which will be restarted upon file changes. Furthermore all tests will be executed whenever you change a file.
You can stop reading right now when you are using the grunt dev task. The
task automatically restarts the server for you.
Automatically restarting the server on file changes is desirable as this increases your development pace. Supervisor can help you with this.
# To install supervisor
npm install -g supervisor
# Then run the server
supervisor src/server.js
Copyright (c) 2013-2014 codecentric AG
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.