danlucraft / git.js Goto Github PK

http://fooo.fr/~vjeux/nodejs/git.js/demos/repo-viewer/index.html

I tried to test the demo but it doesn't work because it gets files in absolute fashion:
GET http://fooo.fr/git.min.js 404 (Not Found)
instead of
http://fooo.fr/~vjeux/nodejs/git.js/lib/git.min.js

Also, the following suggestion would be kickass http://functionsource.com/post/git-js

When I try to use

$ rake demo

I get

~/test/node/git.js$ rake demo --trace
(in /home/ps0ke/test/node/git.js)
** Invoke demo (first_time)
** Invoke package_client (first_time)
** Execute package_client
packaged lib/git.min.js
** Execute demo
rake aborted!
No such file or directory - thin -R demos/config.ru -p 9292 start
/home/ps0ke/test/node/git.js/Rakefile:33:in `exec'
/home/ps0ke/test/node/git.js/Rakefile:33
/usr/lib/ruby/1.8/rake.rb:636:in `call'
/usr/lib/ruby/1.8/rake.rb:636:in `execute'
/usr/lib/ruby/1.8/rake.rb:631:in `each'
/usr/lib/ruby/1.8/rake.rb:631:in `execute'
/usr/lib/ruby/1.8/rake.rb:597:in `invoke_with_call_chain'
/usr/lib/ruby/1.8/monitor.rb:242:in `synchronize'
/usr/lib/ruby/1.8/rake.rb:590:in `invoke_with_call_chain'
/usr/lib/ruby/1.8/rake.rb:583:in `invoke'
/usr/lib/ruby/1.8/rake.rb:2051:in `invoke_task'
/usr/lib/ruby/1.8/rake.rb:2029:in `top_level'
/usr/lib/ruby/1.8/rake.rb:2029:in `each'
/usr/lib/ruby/1.8/rake.rb:2029:in `top_level'
/usr/lib/ruby/1.8/rake.rb:2068:in `standard_exception_handling'
/usr/lib/ruby/1.8/rake.rb:2023:in `top_level'
/usr/lib/ruby/1.8/rake.rb:2001:in `run'
/usr/lib/ruby/1.8/rake.rb:2068:in `standard_exception_handling'
/usr/lib/ruby/1.8/rake.rb:1998:in `run'
/usr/bin/rake:28

I just fetched your repo and so I am for sure on the latest version. I double checked it: demos/config.ru exists!

Could you also write a shot 'How-To' about the usage with node.js, because I don't have any experience with node.js?

1. There should be a package.json file so that it can be published and installed via npm.
2. The dependencies should be loaded as dependencies in the node_modules folder in the node case, and listed in the package.json file. (npm install can pick them all up.)
3. Don't modify require.paths, which is deprecated as of node 0.3, and completely gone in 0.5.
4. Prefer using exports rather than globals.
5. It's be nice to have a node client as well as a server, perhaps even more valuable. (In particular, it'd be really nice to use this in npm for a few things, where I'm instead shelling out to the command line git program.)

It may be worthwhile to check out requirejs or browserify to be able to use exactly the same patterns in both the browser and Node.

Are you still working on this or have you abandoned the idea?

Any plans for supporting a backend that uses the HTML5 filesystem API? Or possibly even local storage somehow? I think this would be very useful, for example to give web apps a git-backed revision system.

Would love to help out with this project somehow, although I am very new to js and not too familiar with git internals.

Eric