https://github.com/brettswift/vagrant-nodejsserver
https://github.com/brettswift/vagrant-nodejsserver
Last synced: about 2 months ago
JSON representation
- Host: GitHub
- URL: https://github.com/brettswift/vagrant-nodejsserver
- Owner: brettswift
- Created: 2013-07-23T12:48:53.000Z (almost 12 years ago)
- Default Branch: develop
- Last Pushed: 2014-12-14T19:09:49.000Z (over 10 years ago)
- Last Synced: 2024-04-14T16:12:01.525Z (about 1 year ago)
- Language: Puppet
- Size: 430 KB
- Stars: 0
- Watchers: 3
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
Vagrant Nodejs Server
=====================
This project bootstraps a Vagrant box with Puppet and Puppet-librarian.
It wraps the brettswift/nodesite puppet module which deploys and configures a nodejs application on a specified version of nodejs.
The nodejs application is configured simply with:
* the git URI
* branch/tag (default: master)
* file to start your web app (default app.js)
###configuration###
`db_connection_string` is passed into the yaml_entries of nodesite. This is the only way to connect uptime to the database currently. Authentication between how mongo is configued via the puppetlabs-mongodb module, and how uptime connects, is not functional.
Run: `vagrant up` and you will have a running nodejs application in under 4 minutes mapped to `http://localhost:8082`.
By default, this is conifigured to run my feature branch of [Uptime](http://redotheweb.com/uptime) hosted on github https://github.com/brettswift/uptime
Git deploys are also enabled by default. The nodesite module will check for upstream changes on each puppet run. If there are any it will run a `git pull`, `npm prune`, `npm install` and restart the service.
Project Structure
-----------------
* `manifests/site.pp` node classification
* `site` local module code
* `modules` installed by librarian-puppet
* `shell` bootstrap provisioners.
* so you can use a clean base vagrant box that doesn't have puppet if you want