nesquena / gitdocs Goto Github PK
View Code? Open in Web Editor NEWOpen-source Dropbox using Ruby and Git
Home Page: https://blog.codepath.com/2011/11/30/collaborate-and-track-tasks-with-ease-using-gitdocs/
License: MIT License
Open-source Dropbox using Ruby and Git
Home Page: https://blog.codepath.com/2011/11/30/collaborate-and-track-tasks-with-ease-using-gitdocs/
License: MIT License
Typo within README (sorry to be that person), near the bottom, where git-annex-assistant is linked it's meant to say "Haskell" not "Haskel". Would have submitted a pull request, but it's a very small issue for a pull request.
It might be useful to include a settings option to change the default port as other programs ( think MAMP ) use :8888 for the localhost.
I test it in a repository at no-master branch.it not work normal.
Should you consider gitdocs for mutil branches in a repository?
It would be nice if files could be deleted from the directory listing rather than having to open a file and delete it. Also, there doesn't seem to be an option to rename the files. Again this would be nice if it could be included in the directory listing.
Hi, great project, which i'd love to start using as soon as this feature is in.
We use dropbox but have the server space (tens of gb) to move to git, but git produces large repos, very quickly, when used with binary data.
Binary data is unfortunately quite common (word/excel/indesign..) and so for it to be usable and not create 100Gb out of a 5gb data within half a year, history dumping is really important.
This has also been discussed in sparkleshare and dismissd, so here's your chance to shine.
I would really love to help with this and have spent hours at the git docs: Alas, my brain is too small, I can not follow into the depths from which the master linus has created this beast.
Conceptionally it's simple: given a time-limit X, you just fold all commits before into one and possibly run gc, Possibly one can just say the last x versions too, whatever makes it easier. But the exact syntax is for someone else to find out.
We could index the files and allows them to be searched and the results displayed. This would be great allowing wikis or files or code snippets (all plain text) to be easily found in a repo. Should be easy if we leverage ack or similar.
When I run gitdocs start
, it claims to start the server and doesn't print any errors, but nothing happens, and subsequent commands make it clear that the server never actually starts.
Note: Seems the issue is linux is not supported just yet
Better documentation using YARD for our codebase.
after i make some changes in monitored directory, commit is done automatically but changes arent pushed to bitbucket, and gitdocs server stops after each of these changes
i initially did
gitdocs create my_local_folder [email protected]:brankito/public_share.git
and started gitdocs server
gitdocs start
then when i add or change some files in my_local_folder commit is realised but nothing pushed to bitbucket, and gitdocs status gives me running:false.
i use SSH, and have added keys as instructed, when i run gitdocs start -D i am being asked to enter passphrase, and when i do it continues asking me to do repeatidly.. maybe this is some clue. Thanks!
EDIT: ok now i know whats problem but dont know how to solve it. the reason while it didnt push is because it ask for passphrase, then it pushes, but then again after a 15sec period(polling_interval) it asks again, so how to store that permanently so it doesnt ask me? thank you.
Once we have the ability to see revision history from the web, we should consider allowing a file to be reverted back to a particular version on the web front-end.
With the currently specified version of Redcarpet specified (2.0.0), Markdown rendering seems to be broken, or at least was for me running Ruby 2.1.0 on ArchLinux.
I'm by no means a Ruby expert, but I got things to work by simply changing
s.add_dependency 'redcarpet', '~> 2.0.0'
to
s.add_dependency 'redcarpet', '~> 3.1.1'
in gitdocs.gemspec, then rake building and installing the new Gem.
This seems to have no ill effects that I've noticed.
Really loving the project so far, thanks for the awesome work :D
I'd love to get this fixed but have been living with it for the time being. I have a repo setup at "/Users/Chris/Gitdocs" its the only repo so if I try to browse the dir contents (http://localhost:8888/0) I see nothing but a blank page. I have a dir inside here called "Notes" if I visit in "http://localhost:8888/0/Notes" all is well and subsequent directories in here work fine. Returning back to the root however returns a blank page again.
Other than that, really loving this :D
I'm note really sure wether this is an git, ruby or your issue but folders containing umlauts like ä and other special characters like ø aren't encoded properly.
In the webinterface, gitdocs display markdown document pretty well -- except those with code block.
Somehow we get used to GitHub flavored markdown, many of our docs have fenced code block or block code. Look good on github but become a mess on gitdoc web preview.
Is it possible to add supports of github flavoured markdown (as mentioned http://railscasts.com/episodes/272-markdown-with-redcarpet?view=asciicast)?
Thanks
It would be nice if gitdocs could give a more informative commit log than the default
"Auto-commit from gitdocs"
A list of the files that were changed/added/deleted would be good.
We have a lot of git commands we use right now directly through the shell. We are better off using grit to power our git usage and avoid the shell altogether. In a future version, let's replace the shell commands with the grit apis.
I´m using gitdocs successfully for my orgmode files, emacs config and dotfiles.
But what bothers me, are the generic commit messages for code changes.
Now it would be very good to set a flag for a new repo to only pull remote changes automatically.
That way one could create real commit messages for certain changes in dotfiles or emacs config
push them manually and they are spread over all machines running gitdocs for the same repository.
I get frequent crashes on my mac (10.6.8, ruby 1.9.3 from macports). When I started in debug mode, after a while I got this error message:
!! Unexpected error while processing request: exit
exit
/macports/lib/ruby1.9/gems/1.9.1/gems/gitdocs-0.4.15/lib/gitdocs/runner.rb:133:in exit' /macports/lib/ruby1.9/gems/1.9.1/gems/gitdocs-0.4.15/lib/gitdocs/runner.rb:133:in
push_changes'
/macports/lib/ruby1.9/gems/1.9.1/gems/gitdocs-0.4.15/lib/gitdocs/runner.rb:65:in block (5 levels) in run' <internal:prelude>:10:in
synchronize'
/macports/lib/ruby1.9/gems/1.9.1/gems/gitdocs-0.4.15/lib/gitdocs/runner.rb:65:in block (4 levels) in run' /macports/lib/ruby1.9/gems/1.9.1/gems/eventmachine-1.0.0.rc.4/lib/eventmachine.rb:1037:in
call'
/macports/lib/ruby1.9/gems/1.9.1/gems/eventmachine-1.0.0.rc.4/lib/eventmachine.rb:1037:in block in spawn_threadpool'127.0.0.1 - - [04/Sep/2012 08:39:57] "GET /xchat2?mode=meta HTTP/1.1" 200 - 0.0400 127.0.0.1 - - [04/Sep/2012 08:39:57] "GET /xmobarrc?mode=meta HTTP/1.1" 200 - 0.0322 127.0.0.1 - - [04/Sep/2012 08:39:57] "GET /xmonad.desktop?mode=meta HTTP/1.1" 200 - 0.0351 127.0.0.1 - - [04/Sep/2012 08:39:57] "GET /xmonad.hs?mode=meta HTTP/1.1" 200 - 0.0507 SystemExit - #<SystemExit: exit> - "exit" /macports/lib/ruby1.9/gems/1.9.1/gems/gitdocs-0.4.15/lib/gitdocs/runner.rb:133:in
exit'
/macports/lib/ruby1.9/gems/1.9.1/gems/gitdocs-0.4.15/lib/gitdocs/runner.rb:133:in push_changes' /macports/lib/ruby1.9/gems/1.9.1/gems/gitdocs-0.4.15/lib/gitdocs/runner.rb:65:in
block (5 levels) in run'
internal:prelude:10:in synchronize' /macports/lib/ruby1.9/gems/1.9.1/gems/gitdocs-0.4.15/lib/gitdocs/runner.rb:65:in
block (4 levels) in run'
/macports/lib/ruby1.9/gems/1.9.1/gems/eventmachine-1.0.0.rc.4/lib/eventmachine.rb:1037:in call' /macports/lib/ruby1.9/gems/1.9.1/gems/eventmachine-1.0.0.rc.4/lib/eventmachine.rb:1037:in
block in spawn_threadpool'
Gitdocs is terminating...goodbye
Installing the latest prerelease 3 yesterday, I have run into some serious problems. I'm running gitdocs on updated Debian wheezy and Arch Linux systems. gitdocs pre3 takes 100% cpu and is slowly filling up my $HOME. I can't see where, but in my one and only share temporary files are continuously being created (but also removed) in .git/objects/.
I'm not touching the actual files in my share during all this.
On my Debian server, gitdocs eventually crashes after around 30 minutes, with log output as below. On the client I had to slay the hogging process before that... I tried with start -D but get nothing there.
I, [2014-04-04T06:30:06.729134 #21650] INFO -- : Starting Gitdocs v0.5.0.pre3...
I, [2014-04-04T06:30:06.729963 #21650] INFO -- : Using configuration root: '/home/quite/.gitdocs'
I, [2014-04-04T06:30:06.820999 #21650] INFO -- : Shares: (1) #<Gitdocs::Configuration::Share id: 1, path: "/home/quite/gitdocs/depo", polling_interval: 15.0, notification: false, remote_name: "origin", branch_name: "master">
I, [2014-04-04T06:30:06.821824 #21650] INFO -- : Starting EM loop...
I, [2014-04-04T06:30:28.477166 #21650] INFO -- : Web server running!
E, [2014-04-04T07:02:04.864785 #21650] ERROR -- : Exception - #<Exception: inotify event queue has overflowed.> - "inotify event queue has overflowed."
E, [2014-04-04T07:02:04.898470 #21650] ERROR -- : /home/quite/.gem/ruby/1.9.1/gems/joshbuddy-guard-0.10.0/lib/vendor/linux/lib/rb-inotify/event.rb:120:in `initialize'
/home/quite/.gem/ruby/1.9.1/gems/joshbuddy-guard-0.10.0/lib/vendor/linux/lib/rb-inotify/event.rb:100:in `new'
/home/quite/.gem/ruby/1.9.1/gems/joshbuddy-guard-0.10.0/lib/vendor/linux/lib/rb-inotify/event.rb:100:in `consume'
/home/quite/.gem/ruby/1.9.1/gems/joshbuddy-guard-0.10.0/lib/vendor/linux/lib/rb-inotify/notifier.rb:272:in `read_events'
/home/quite/.gem/ruby/1.9.1/gems/joshbuddy-guard-0.10.0/lib/vendor/linux/lib/rb-inotify/notifier.rb:233:in `process'
/home/quite/.gem/ruby/1.9.1/gems/joshbuddy-guard-0.10.0/lib/guard/listeners/linux.rb:81:in `watch_change'
/home/quite/.gem/ruby/1.9.1/gems/joshbuddy-guard-0.10.0/lib/guard/listeners/linux.rb:21:in `start'
/home/quite/.gem/ruby/1.9.1/gems/gitdocs-0.5.0.pre3/lib/gitdocs/runner.rb:55:in `block in run'
/home/quite/.gem/ruby/1.9.1/gems/eventmachine-1.0.3/lib/eventmachine.rb:1037:in `call'
/home/quite/.gem/ruby/1.9.1/gems/eventmachine-1.0.3/lib/eventmachine.rb:1037:in `block in spawn_threadpool'
I, [2014-04-04T07:02:05.247147 #21650] INFO -- : Gitdocs is terminating...goodbye
I just installed gitdocs on Mac OS X 10.6.8 (32 bit) and whenever I type gitdocs start I'm getting a "Failed to start gitdocs" error message.
gitdocs start -D gives me the following error:
Starting in debug mode
Starting Gitdocs v0.4.14...
Using configuration root: '/Users/patrick/.gitdocs'
Shares: #<Gitdocs::Configuration::Share id: 1, path: "/Users/patrick/Documents/gitdocs", polling_interval: 15.0, notification: true, remote_name: "origin", branch_name: "master">
Starting EM loop...
Starting #<Gitdocs::Configuration::Share:0x237a0d0>
Running runners... 1
Errno::E086 - #<Errno::E086: Bad CPU type in executable - /Users/patrick/.rvm/gems/ruby-1.9.3-p194/gems/joshbuddy-guard-0.10.0/bin/fsevent_watch_guard> - "Bad CPU type in executable - /Users/patrick/.rvm/gems/ruby-1.9.3-p194/gems/joshbuddy-guard-0.10.0/bin/fsevent_watch_guard"
/Users/patrick/.rvm/gems/ruby-1.9.3-p194/gems/joshbuddy-guard-0.10.0/lib/vendor/darwin/lib/rb-fsevent/fsevent.rb:89:in `popen'
/Users/patrick/.rvm/gems/ruby-1.9.3-p194/gems/joshbuddy-guard-0.10.0/lib/vendor/darwin/lib/rb-fsevent/fsevent.rb:89:in `pipe'
/Users/patrick/.rvm/gems/ruby-1.9.3-p194/gems/joshbuddy-guard-0.10.0/lib/vendor/darwin/lib/rb-fsevent/fsevent.rb:46:in `stop'
/Users/patrick/.rvm/gems/ruby-1.9.3-p194/gems/joshbuddy-guard-0.10.0/lib/vendor/darwin/lib/rb-fsevent/fsevent.rb:42:in `ensure in run'
/Users/patrick/.rvm/gems/ruby-1.9.3-p194/gems/joshbuddy-guard-0.10.0/lib/vendor/darwin/lib/rb-fsevent/fsevent.rb:42:in `run'
/Users/patrick/.rvm/gems/ruby-1.9.3-p194/gems/joshbuddy-guard-0.10.0/lib/guard/listeners/darwin.rb:18:in `start'
/Users/patrick/.rvm/gems/ruby-1.9.3-p194/gems/gitdocs-0.4.14/lib/gitdocs/runner.rb:70:in `block in run'
/Users/patrick/.rvm/gems/ruby-1.9.3-p194/gems/eventmachine-1.0.0.beta.4/lib/eventmachine.rb:1012:in `call'
/Users/patrick/.rvm/gems/ruby-1.9.3-p194/gems/eventmachine-1.0.0.beta.4/lib/eventmachine.rb:1012:in `block in spawn_threadpool'
Gitdocs is terminating...goodbye
/Users/patrick/.rvm/gems/ruby-1.9.3-p194/gems/joshbuddy-guard-0.10.0/lib/vendor/darwin/lib/rb-fsevent/fsevent.rb:89:in `popen': Bad CPU type in executable - /Users/patrick/.rvm/gems/ruby-1.9.3-p194/gems/joshbuddy-guard-0.10.0/bin/fsevent_watch_guard (Errno::E086)
from /Users/patrick/.rvm/gems/ruby-1.9.3-p194/gems/joshbuddy-guard-0.10.0/lib/vendor/darwin/lib/rb-fsevent/fsevent.rb:89:in `pipe'
from /Users/patrick/.rvm/gems/ruby-1.9.3-p194/gems/joshbuddy-guard-0.10.0/lib/vendor/darwin/lib/rb-fsevent/fsevent.rb:46:in `stop'
from /Users/patrick/.rvm/gems/ruby-1.9.3-p194/gems/joshbuddy-guard-0.10.0/lib/vendor/darwin/lib/rb-fsevent/fsevent.rb:42:in `ensure in run'
from /Users/patrick/.rvm/gems/ruby-1.9.3-p194/gems/joshbuddy-guard-0.10.0/lib/vendor/darwin/lib/rb-fsevent/fsevent.rb:42:in `run'
from /Users/patrick/.rvm/gems/ruby-1.9.3-p194/gems/joshbuddy-guard-0.10.0/lib/guard/listeners/darwin.rb:18:in `start'
from /Users/patrick/.rvm/gems/ruby-1.9.3-p194/gems/gitdocs-0.4.14/lib/gitdocs/runner.rb:70:in `block in run'
from /Users/patrick/.rvm/gems/ruby-1.9.3-p194/gems/eventmachine-1.0.0.beta.4/lib/eventmachine.rb:1012:in `call'
from /Users/patrick/.rvm/gems/ruby-1.9.3-p194/gems/eventmachine-1.0.0.beta.4/lib/eventmachine.rb:1012:in `block in spawn_threadpool'
I just installed gitdocs and tried to start the frontend but starting fails with the following output:
Starting Gitdocs v0.4.15...
Using configuration root: '/Users/gilligan/.gitdocs'
Shares: #<Gitdocs::Configuration::Share id: 1, path: "/Users/gilligan/notes", polling_interval: 15.0, notification: true, remote_name: "origin", branch_name: "master">
Starting EM loop...
Starting #<Gitdocs::Configuration::Share:0x007ff0ee98f490>
Running runners... 1
>> Thin web server (v1.3.1 codename Triple Espresso)
>> Debugging ON
>> Maximum connections set to 1024
>> Listening on 127.0.0.1:8888, CTRL+C to stop
Web server running!
127.0.0.1 - - [26/Mar/2013 21:17:40] "GET / HTTP/1.1" 302 - 0.0018
!! Unexpected error while processing request: Template engine not found: :txt
Template engine not found: :txt
/usr/local/var/rbenv/versions/2.0.0-p0/lib/ruby/gems/2.0.0/gems/renee-render-0.3.11/lib/renee_render.rb:91:in `block (2 levels) in render'
/usr/local/var/rbenv/versions/2.0.0-p0/lib/ruby/gems/2.0.0/gems/tilt-1.3.6/lib/tilt.rb:127:in `fetch'
/usr/local/var/rbenv/versions/2.0.0-p0/lib/ruby/gems/2.0.0/gems/renee-render-0.3.11/lib/renee_render.rb:88:in `block in render'
/usr/local/var/rbenv/versions/2.0.0-p0/lib/ruby/gems/2.0.0/gems/renee-render-0.3.11/lib/renee_render.rb:175:in `render_setup'
/usr/local/var/rbenv/versions/2.0.0-p0/lib/ruby/gems/2.0.0/gems/renee-render-0.3.11/lib/renee_render.rb:87:in `render'
/usr/local/var/rbenv/versions/2.0.0-p0/lib/ruby/gems/2.0.0/gems/gitdocs-0.4.15/lib/gitdocs/server.rb:105:in `block (3 levels) in start'
/usr/local/var/rbenv/versions/2.0.0-p0/lib/ruby/gems/2.0.0/gems/renee-core-0.3.11/lib/renee_core/routing.rb:271:in `block in complex_variable'
/usr/local/var/rbenv/versions/2.0.0-p0/lib/ruby/gems/2.0.0/gems/renee-core-0.3.11/lib/renee_core/routing.rb:312:in `with_path_part'
/usr/local/var/rbenv/versions/2.0.0-p0/lib/ruby/gems/2.0.0/gems/renee-core-0.3.11/lib/renee_core/routing.rb:269:in `complex_variable'
/usr/local/var/rbenv/versions/2.0.0-p0/lib/ruby/gems/2.0.0/gems/renee-core-0.3.11/lib/renee_core/routing.rb:71:in `variable'
/usr/local/var/rbenv/versions/2.0.0-p0/lib/ruby/gems/2.0.0/gems/renee-core-0.3.11/lib/renee_core/chaining.rb:51:in `var'
/usr/local/var/rbenv/versions/2.0.0-p0/lib/ruby/gems/2.0.0/gems/gitdocs-0.4.15/lib/gitdocs/server.rb:69:in `block (2 levels) in start'
/usr/local/var/rbenv/versions/2.0.0-p0/lib/ruby/gems/2.0.0/gems/renee-core-0.3.11/lib/renee_core/request_context.rb:16:in `instance_eval'
/usr/local/var/rbenv/versions/2.0.0-p0/lib/ruby/gems/2.0.0/gems/renee-core-0.3.11/lib/renee_core/request_context.rb:16:in `block in call'
/usr/local/var/rbenv/versions/2.0.0-p0/lib/ruby/gems/2.0.0/gems/renee-core-0.3.11/lib/renee_core/request_context.rb:14:in `catch'
/usr/local/var/rbenv/versions/2.0.0-p0/lib/ruby/gems/2.0.0/gems/renee-core-0.3.11/lib/renee_core/request_context.rb:14:in `call'
/usr/local/var/rbenv/versions/2.0.0-p0/lib/ruby/gems/2.0.0/gems/renee-core-0.3.11/lib/renee_core.rb:38:in `call'
/usr/local/var/rbenv/versions/2.0.0-p0/lib/ruby/gems/2.0.0/gems/rack-1.3.10/lib/rack/methodoverride.rb:24:in `call'
/usr/local/var/rbenv/versions/2.0.0-p0/lib/ruby/gems/2.0.0/gems/rack-1.3.10/lib/rack/static.rb:53:in `call'
/usr/local/var/rbenv/versions/2.0.0-p0/lib/ruby/gems/2.0.0/gems/rack-1.3.10/lib/rack/commonlogger.rb:20:in `call'
/usr/local/var/rbenv/versions/2.0.0-p0/lib/ruby/gems/2.0.0/gems/thin-1.3.1/lib/thin/connection.rb:80:in `block in pre_process'
/usr/local/var/rbenv/versions/2.0.0-p0/lib/ruby/gems/2.0.0/gems/thin-1.3.1/lib/thin/connection.rb:78:in `catch'
/usr/local/var/rbenv/versions/2.0.0-p0/lib/ruby/gems/2.0.0/gems/thin-1.3.1/lib/thin/connection.rb:78:in `pre_process'
/usr/local/var/rbenv/versions/2.0.0-p0/lib/ruby/gems/2.0.0/gems/thin-1.3.1/lib/thin/connection.rb:53:in `process'
/usr/local/var/rbenv/versions/2.0.0-p0/lib/ruby/gems/2.0.0/gems/thin-1.3.1/lib/thin/connection.rb:38:in `receive_data'
/usr/local/var/rbenv/versions/2.0.0-p0/lib/ruby/gems/2.0.0/gems/eventmachine-1.0.3/lib/eventmachine.rb:187:in `run_machine'
/usr/local/var/rbenv/versions/2.0.0-p0/lib/ruby/gems/2.0.0/gems/eventmachine-1.0.3/lib/eventmachine.rb:187:in `run'
/usr/local/var/rbenv/versions/2.0.0-p0/lib/ruby/gems/2.0.0/gems/gitdocs-0.4.15/lib/gitdocs/manager.rb:34:in `start'
/usr/local/var/rbenv/versions/2.0.0-p0/lib/ruby/gems/2.0.0/gems/gitdocs-0.4.15/lib/gitdocs.rb:26:in `start'
/usr/local/var/rbenv/versions/2.0.0-p0/lib/ruby/gems/2.0.0/gems/gitdocs-0.4.15/lib/gitdocs/cli.rb:18:in `start'
/usr/local/var/rbenv/versions/2.0.0-p0/lib/ruby/gems/2.0.0/gems/thor-0.14.6/lib/thor/task.rb:22:in `run'
/usr/local/var/rbenv/versions/2.0.0-p0/lib/ruby/gems/2.0.0/gems/thor-0.14.6/lib/thor/invocation.rb:118:in `invoke_task'
/usr/local/var/rbenv/versions/2.0.0-p0/lib/ruby/gems/2.0.0/gems/thor-0.14.6/lib/thor.rb:263:in `dispatch'
/usr/local/var/rbenv/versions/2.0.0-p0/lib/ruby/gems/2.0.0/gems/thor-0.14.6/lib/thor/base.rb:389:in `start'
/usr/local/var/rbenv/versions/2.0.0-p0/lib/ruby/gems/2.0.0/gems/gitdocs-0.4.15/bin/gitdocs:5:in `<top (required)>'
/usr/local/var/rbenv/versions/2.0.0-p0/bin/gitdocs:23:in `load'
/usr/local/var/rbenv/versions/2.0.0-p0/bin/gitdocs:23:in `<main>'
I'm running OSX/ruby 2.0.0p0 (2013-02-24 revision 39474) [x86_64-darwin12.2.1]
Hi guys, I would like to give gitdocs a shot and in the process to write an ebuild (default Gentoo package atom) for it. Are there any instructions on installing gitdocs from source which I could follow?
So I can have my gitdocs root listing at http://example.com/my/
Or is this possible somehow?
I would like to apply most, but probably not all, of the rules from https://github.com/bbatsov/ruby-style-guide primarily by using the https://github.com/bbatsov/rubocop gem.
(One example to disable would be the HashSyntax offence, which expects the Ruby1.9 syntax)
I wanted to check to see if this seems like a good ideas before put any time into this. :)
E, [2013-08-01T20:59:54.235096 #3541] ERROR -- : RuntimeError - #<RuntimeError: # On branch master
nothing to commit, working directory clean
- "# On branch master\nnothing to commit, working directory clean\n"
E, [2013-08-01T20:59:54.236724 #3541] ERROR -- : /home/quite/.gem/ruby/2.0.0/gems/shell_tools-0.1.2/lib/shell_tools.rb:8:insh' /home/quite/.gem/ruby/2.0.0/gems/gitdocs-0.4.15/lib/gitdocs/runner.rb:121:in
push_changes'
/home/quite/.gem/ruby/2.0.0/gems/gitdocs-0.4.15/lib/gitdocs/runner.rb:65:inblock (5 levels) in run' /home/quite/.gem/ruby/2.0.0/gems/gitdocs-0.4.15/lib/gitdocs/runner.rb:65:in
synchronize'
/home/quite/.gem/ruby/2.0.0/gems/gitdocs-0.4.15/lib/gitdocs/runner.rb:65:inblock (4 levels) in run' /home/quite/.gem/ruby/2.0.0/gems/eventmachine-1.0.3/lib/eventmachine.rb:1037:in
call'
/home/quite/.gem/ruby/2.0.0/gems/eventmachine-1.0.3/lib/eventmachine.rb:1037:in `block in spawn_threadpool'
I, [2013-08-01T20:59:54.236860 #3541] INFO -- : Gitdocs is terminating...goodbye
Removing paths does not work in version 0.3.1
When executing "gitdocs start" in 64-bit Win7 using Ruby 1.9.2p290, I get this backtrace due to dante trying to fork().
C:/Ruby192/lib/ruby/gems/1.9.1/gems/dante-0.1.2/lib/dante/runner.rb:66:in 'fork': fork() function is unimplemented on this machine (NotImplementedError)
from C:/Ruby192/lib/ruby/gems/1.9.1/gems/dante-0.1.2/lib/dante/runner.rb:66:in 'daemonize'
from C:/Ruby192/lib/ruby/gems/1.9.1/gems/dante-0.1.2/lib/dante/runner.rb:58:in 'execute'
from C:/Ruby192/lib/ruby/gems/1.9.1/gems/gitdocs-0.4.7/lib/gitdocs/cli.rb:13:in 'start'
from C:/Ruby192/lib/ruby/gems/1.9.1/gems/thor-0.14.6/lib/thor/task.rb:22:in 'run'
from C:/Ruby192/lib/ruby/gems/1.9.1/gems/thor-0.14.6/lib/thor/invocation.rb:118:in 'invoke_task'
from C:/Ruby192/lib/ruby/gems/1.9.1/gems/thor-0.14.6/lib/thor.rb:263:in 'dispatch'
from C:/Ruby192/lib/ruby/gems/1.9.1/gems/thor-0.14.6/lib/thor/base.rb:389:in 'start'
from C:/Ruby192/lib/ruby/gems/1.9.1/gems/gitdocs-0.4.7/bin/gitdocs:5:in '<top (required)>'
from C:/Ruby192/bin/gitdocs:19:in 'load'
from C:/Ruby192/bin/gitdocs:19:in '<main>'
We could use localtunnel or some other means to allow a user to 'public' share and then give a url which other users can access. Or maybe we should just avoid this? Not sure.
I would like to do some refactoring in the gitdocs UI, and I wonder if we should the web framework first.
@nesquena or @joshbuddy do you consider Renee to still be supported? I see that it has been in pre-release since 2012, and according to rubytoolbox it is only being used by gitdocs.
What would you think of switching to Sintara? (Padrino would be an option, but my first instinct is that it probably more heavy than necessary for this gitdocs.)
Looks like I have mis-used the Rugged conflict entires, and non-conflicted files can get marked as conflict when there are conflicted files.
I am working on a fix and I will have a PR as soon as I can.
Should be able to add or remove paths via the web interface in settings
Be able to edit files in the web front-end using the ace text editor and sytntax highlighting. Brewing in https://github.com/bazaarlabs/gitdocs/tree/edit_files branch.
Also support uploading and deleting files in web front-end
Right now Gitdocs does not tell me when it quits because of error, if I don't have notifications on. So I can only choose between a constant stream of update notifications and periodically having to check if Gitdocs is still running manually.
If Gitdocs quits without me noticing it will probably mean that I will lose file revisions. Not cool.
Because of this I request that Gitdocs will make an effort to let me know when it quits. Growl notification, some kind of sound or anything as long as it keeps me from potentially losing data.
That would make a great tool even better. Thanks.
We should support windows at some point.
I'm using gitdocs
on OS X 10.9.2 through Homebrew ruby. I do:
$ gitdocs start -D
The web server (v1.3.1) starts, and handles a few requests, but then:
SystemExit - #<SystemExit: exit> - "exit"
/usr/local/Cellar/ruby/2.1.0/lib/ruby/gems/2.1.0/gems/gitdocs-0.4.15/lib/gitdocs/runner.rb:133:in `exit'
/usr/local/Cellar/ruby/2.1.0/lib/ruby/gems/2.1.0/gems/gitdocs-0.4.15/lib/gitdocs/runner.rb:133:in `push_changes'
/usr/local/Cellar/ruby/2.1.0/lib/ruby/gems/2.1.0/gems/gitdocs-0.4.15/lib/gitdocs/runner.rb:86:in `sync_changes'
/usr/local/Cellar/ruby/2.1.0/lib/ruby/gems/2.1.0/gems/gitdocs-0.4.15/lib/gitdocs/runner.rb:47:in `block (3 levels) in run'
/usr/local/Cellar/ruby/2.1.0/lib/ruby/gems/2.1.0/gems/gitdocs-0.4.15/lib/gitdocs/runner.rb:47:in `synchronize'
/usr/local/Cellar/ruby/2.1.0/lib/ruby/gems/2.1.0/gems/gitdocs-0.4.15/lib/gitdocs/runner.rb:47:in `block (2 levels) in run'
/usr/local/Cellar/ruby/2.1.0/lib/ruby/gems/2.1.0/gems/eventmachine-1.0.3/lib/eventmachine.rb:1037:in `call'
/usr/local/Cellar/ruby/2.1.0/lib/ruby/gems/2.1.0/gems/eventmachine-1.0.3/lib/eventmachine.rb:1037:in `block in spawn_threadpool'
Gitdocs is terminating...goodbye
Should we support repo submodules
Git has rich revision history. Using grit, we should be able to retrieve and display that on the web front-end, allowing people to view the history of a file.
I'm the author of bitpocket (https://github.com/sickill/bitpocket), rsync-based solution for 2 way syncing, very similar to LipSync.
You have a list of other alternatives in your project's readme and it would be cool if you added bitpocket to the list.
Dotfiles seem to work in the repo, and in the web interface if I go to the directory manually (by editing the URL), but they don't seem to show in the default listing on the web interface, when I go to http://localhost:8888/.
You should be able to set polling interval, notifications, etc for a repo using the cli?
gitdocs config polling.interval --set 5
gitdocs config polling.interval
gitdocs config polling.interval --global
gitdocs config -l # list all?
brew install growlnotify returns
Error: No available formula for growlnotify
But the DMG for growl notify still exits
http://growl.cachefly.net/GrowlNotify-1.3.zip
I was taking a look at the project and I noticed that you can add paths to be watched by gitdocs, but if the path dont have git repository it shows an error in the debugger mode
I think that when you try to add a path to be watched i should detect if it has a git repo already or prompt for creating one
When following the directions on the projects github homepage, using the bitbucket site, and making a ~/Documents/gitdocs, etc, etc.
As soon as the repo is adding, a constant loop of notifications informing me that the repo can't be synced.
Then when I added my first file, it just keeps endlessly notifying me that the file pushed. "Pushed 0 Changes"
This just continues to loop forever.
Stopping and starting gitdocs seems to fix this, but not sure why it happens.
I have a repository on a server, and run gitdocs on both the server and a "client". Both push fine to the repo, but the gitdocs instance on the server doesn't seem to pull. Only when I do a gitdocs restart there, I get the new commits. How can I debug?
(pushing to the repo is fine on both client and server--I see almost instant updates to the repo on the server)
I use sparkleshare on a client to push files & folders to a git and use gitdocs on this server to pull those elements to another directory (as sparkleshare has no command line mode). Works so far so good :-)
Anyhow somethings messed up with the rights of the folders & files once gitdocs pulls them. On the initial checkout with gitdocs everything is fine.
But as soon as I create a new file or folder on the sparkleshare side and gitdocs got the file or folder it will gain an extra +w. So a folder created with drwxrwxr-x will be drwxrwxrwx afterwards. The same goes for files a file created with -rw-rw-r-- will be -rw-rw-rw- after the pull of gitdocs.
When I use sparkleshare on another client this doesn't happen. I looked through server.rb but wasn't able to find why the rights are changed. Anyone an idea?
After editing the name of a file and trying to view the newly named file via the browser I'm seeing the message:
Got java.io.EOFException (Server closed connection while sending the HTTP header.): http://localhost:8888/0/computing/server/basic-server-setup.md
This is also happening on a couple of other files I have renamed. I can't work out the exact trigger of it. It would seeming renaming files then trying to access them via their new name sometimes works and sometimes produces the error above.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.