apollo-ng / dspace-app-apollong

DSpace aims to enable people to find, collect, edit, structure and share any kind of information in a real-time, massive-collaboration, augmented-reality-environment (like wikipedia), based on a very common ground: The map of the area, where people actually are, around their Geolocation.
https://apollo.open-resource.org/lab:dspace
18 stars 13 forks source link

build instructions, e.g. INSTALL.md #81

Closed guaka closed 10 years ago

guaka commented 11 years ago

It would be useful to have a basic INSTALL.md with some instructions on how to run this.

Now I get:

$ make
-n Building Ender...

module.js:340
    throw err;
          ^
Error: Cannot find module '/Users/guaka/playground/dspace-client/node_modules/.bin/ender'
    at Function.Module._resolveFilename (module.js:338:15)
    at Function.Module._load (module.js:280:25)
    at Module.runMain (module.js:492:10)
    at process.startup.processNextTick.process._tickCallback (node.js:244:9)
make: *** [ender] Error 1
guaka commented 11 years ago

after npm install ender I get a wee bit further

$ make
-n Building Ender...
npm http GET https://registry.npmjs.org/bonzo
npm http GET https://registry.npmjs.org/bean
npm http GET https://registry.npmjs.org/domready
npm http GET https://registry.npmjs.org/qwery
npm http GET https://registry.npmjs.org/morpheus
npm http GET https://registry.npmjs.org/ender-js
npm http 200 https://registry.npmjs.org/domready
npm http GET https://registry.npmjs.org/domready/-/domready-0.2.11.tgz
npm http 200 https://registry.npmjs.org/morpheus
npm http GET https://registry.npmjs.org/morpheus/-/morpheus-0.6.7.tgz
npm http 200 https://registry.npmjs.org/qwery
npm http GET https://registry.npmjs.org/qwery/-/qwery-3.4.1.tgz
npm http 200 https://registry.npmjs.org/ender-js
npm http GET https://registry.npmjs.org/ender-js/-/ender-js-0.4.4-1.tgz
npm http 200 https://registry.npmjs.org/bonzo
npm http GET https://registry.npmjs.org/bonzo/-/bonzo-1.3.4.tgz
npm http 200 https://registry.npmjs.org/bean
npm http GET https://registry.npmjs.org/bean/-/bean-1.0.3.tgz
sed: 1: "ender.js": invalid command code e
make: *** [ender] Error 1
$ make
-n Building Ender...
sed: 1: "ender.js": invalid command code e
make: *** [ender] Error 1
elf-pavlik commented 11 years ago

@guaka have you followed: https://github.com/apollo-ng/dspace-client#dev ? :)

guaka commented 11 years ago

Ah no, cool!

I think this could be a little bit more verbose though. E.g. add the word "installation" or "install" somewhere :)

And I still get stuck:

$ make deps
-n Building Ender...
sed: 1: "ender.js": invalid command code e
make: *** [ender] Error 1
elf-pavlik commented 11 years ago

@guaka since we work just on client componen, one needs to take all those steps only for development, for simple use @alice-wl works on android wrapper and later we can look at ways to distribute it as packaged web app ping @nilclass

checking make deps issue now!

elf-pavlik commented 11 years ago

@guaka it should work if you just do

./run.js

and visit localhost as it suggest :)

we should add to README ### run section above ###dev

thanks for feedback!

guaka commented 11 years ago

./run.js works but localhost:3000 is stuck with this:

Screen Shot 2013-03-20 at 11 52 35 PM

elf-pavlik commented 11 years ago

@guaka any errors in browser's console? just ping me on jabber if you like and we can deal with it together!

guaka commented 11 years ago

Yep:

Failed to load resource: the server responded with a status of 404 (Not Found) http://localhost:3000/deps/require.js Uncaught ReferenceError: requirejs is not defined

On Thu, Mar 21, 2013 at 10:36 AM, elf Pavlik notifications@github.comwrote:

@guaka https://github.com/guaka any errors in browser's console?

— Reply to this email directly or view it on GitHubhttps://github.com/apollo-ng/dspace-client/issues/81#issuecomment-15226962 .

realitygaps commented 11 years ago

I have the same error on the develop branch

chron0 commented 11 years ago

Yeah, my bad. I've been vigorously testing the dev/build process in the past to make sure stuff like that didn't happen, because once you are set up you never issues like that anymore. When we change something in the process then, we mostly wouldn't realize that it was broken, because we already have it set up. I'll start with a naked setup again, to find out why it fails. It is most likely linked to the issue with the demo, since the deploy is broken there as well. Sorry for the delay on feedback and the lack of bare init testing :)

chron0 commented 11 years ago

@nilclass debugged the build process and fixed some issues, another bare-repo init test was also successfull. Could you guys please try again, and make sure not to use anything above NodeJS 0.8.x? I will close the ticket here when I've moved the stuff into INSTALL.MD :)

chron0 commented 11 years ago

Ok, Done now. Could you please test again, if it works now when using the Installation walktrough in INSTALL.md? The build has been tested here successfully so it should work for you too. Don't hesitate to ask any question, when you get stuck, so that we can update the docs on parts that are not clear.