Skip to content
Browse files

Added some packaginess

  • Loading branch information...
1 parent 8c6e9dd commit 65628137f2129ab9887f2026299dd046eeee9a70 @rclark rclark committed Mar 1, 2012
Showing with 60 additions and 0 deletions.
  1. +37 −0 README.md
  2. +23 −0 package.json
View
37 README.md
@@ -0,0 +1,37 @@
+# USGIN METADTA MANAGER
+
+A web application for managing metadata. We built it because we wanted good control over the format of the metadata
+that we have to manage, we wanted a simple user-interface that doesn't use anything fancier than HTML, Javascript and
+CSS, and we also wanted a great way to transform our metadata into whatever standard format we'd like to.
+
+## Installation
+### Prerequisites:
+1. Node.js and NPM
+2. CouchDB and couchdb-lucene
+3. Expat and Node dev libraries
+
+### Installation procedure
+1. Get the code and install the dependancies:
+
+ git clone git://github.com/usgin/resources.git
+ cd resources
+ npm install
+
+2. Create a configuration file just for you:
+
+ cd server/configuration
+ cp config-example.js config
+
+3. Adjust the config.js file to suit your purposes.
+4. Run the setup routine
+
+ node setup.js
+
+## Run the application
+First, make sure that you've got couchdb-lucene running. Then:
+
+ cd resources/server
+ node main.js
+
+Your application should be available at `http://<your config'd servername>:<you config'd server port>`
+
View
23 package.json
@@ -0,0 +1,23 @@
+{
+ "author": "Ryan Clark and Genhan Chen <ryan.clark@azgs.az.gov>",
+ "name": "usginmeta",
+ "description": "Metadata manager developed for USGIN",
+ "version": "0.1.0",
+ "homepage": "http://github.com/usgin/resources",
+ "repository": {
+ "type": "git",
+ "url": "git://github.com/usgin/resources.git"
+ },
+ "main": "server/main.js",
+ "engines": {
+ "node": "~0.4.9"
+ },
+ "dependencies": {
+ "connect-auth": ">= 0.4.1",
+ "cradle": ">= 0.5.8",
+ "express": ">= 2.5.8",
+ "jade": ">= 0.20.3",
+ "xml2json": ">= 0.2.4"
+ },
+ "devDependencies": {}
+}

0 comments on commit 6562813

Please sign in to comment.
Something went wrong with that request. Please try again.