tforgione
/
3d-interface
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
642 Commits 1 Branch 0 Tags 30 MiB
JavaScript 89.7%
Pug 6.2%
CSS 1.3%
PLpgSQL 1.1%
Makefile 0.8%
Other 0.9%
Go to file
Thomas FORGIONE e5eacddc58 Monster commit 
- New analysis functions
- Scene rotation and scale done server side
- PGSQL files are now launchable
- New sql queries
- Removed dependancy from ip
 		2015-10-20 16:30:52 +02:00
403 Fixed reload that doesn't work 😢 2015-06-30 09:42:24 +02:00
analysis Monster commit 2015-10-20 16:30:52 +02:00
controllers Corrected problem 2015-10-09 10:01:53 +02:00
geo Monster commit 2015-10-20 16:30:52 +02:00
js Monster commit 2015-10-20 16:30:52 +02:00
lib JSHint cleaning 2015-10-06 16:58:04 +02:00
posts Better mail (easier to treat automatically) 2015-10-06 13:48:58 +02:00
sql Monster commit 2015-10-20 16:30:52 +02:00
static Added check.sh, and gitignores 2015-10-06 16:50:45 +02:00
utils Preparing for local demo 2015-10-13 16:29:41 +02:00
views Remove link 2015-10-13 08:48:48 +02:00
.gitignore Added check.sh, and gitignores 2015-10-06 16:50:45 +02:00
README.md Inotifywait 2015-10-06 15:00:22 +02:00
npm-shrinkwrap.json Continuing on micro workers, and corrected some bugs 2015-09-29 17:22:48 +02:00
package.json Continuing on micro workers, and corrected some bugs 2015-09-29 17:22:48 +02:00
server.js Monster commit 2015-10-20 16:30:52 +02:00
socket.js Added log module 2015-07-03 13:27:05 +02:00
urls.js From mixed convetion (_, and camel case) to all camel case 2015-08-28 21:34:29 +02:00

README.md

3D Interface

A prototype for a user-friendly 3D interface allowing to browse 3D scenes / models written with Node.js.

It is hosted by OpenShift at 3dinterface.no-ip.org.

Database setup

First you need to configure the database. You can create a postgres database where you want, and you can initialize it by running the script sql/backup.pgsql.

Nodejs configuration

Then, you have to set up nodejs to access to your database. Basically, you have to create a file private.js at the root of the repository looking like this :

module.exports.url = ... // the url to connect to your database

module.exports.secret = ... // A secret string used to hash stuff

Compiling the static js files

First, cd to utils/. Here you'll find a script build_all.sh that, as its name suggests, builds all. By default, it minifies the code, but you can pass the option --dev to avoid minifying (which is a quite long operation).

If it worked, you should see lots of files in *.min.js in your static/js directory, and a geo.min.js in your lib (at the root of the repository).

Running the server

As usual with NodeJS, it's quite easy to test. Just ensure you have node installed on your machine, clone this repo somewhere, and then, in the repo do

npm install
node server.js

You should be able to go to localhost:4000 and see the result.

Please note that some static files (some meshes / textures) are not on this repository (especially the heavy ones).

Developping

If you want to dev on this project, the utils/demon.sh may help you : it is based on nodemon (that basically restarts the server everytime there is a change in the code) and inotifywait (that basically recompiles everything when there is a modification). To use it, just cd to utils and run demon.sh (note that it doesn't minify the code since this operation is heavy and too long to redo everytime there is a change).