gitdocs 0.1.4 → 0.1.5

Sign up to get free protection for your applications and to get access to all the features.
data/LICENSE ADDED
@@ -0,0 +1,20 @@
1
+ Copyright (c) 2011 GoMiso, Inc
2
+
3
+ Permission is hereby granted, free of charge, to any person obtaining
4
+ a copy of this software and associated documentation files (the
5
+ "Software"), to deal in the Software without restriction, including
6
+ without limitation the rights to use, copy, modify, merge, publish,
7
+ distribute, sublicense, and/or sell copies of the Software, and to
8
+ permit persons to whom the Software is furnished to do so, subject to
9
+ the following conditions:
10
+
11
+ The above copyright notice and this permission notice shall be
12
+ included in all copies or substantial portions of the Software.
13
+
14
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
15
+ EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
16
+ MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
17
+ NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
18
+ LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
19
+ OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
20
+ WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
data/README.md CHANGED
@@ -2,8 +2,7 @@
2
2
 
3
3
  Collaborate on files and docs through a shared git repository. gitdocs will automatically push changes to the repo as well as pull in changes.
4
4
  This allows any git repo to be used as a collaborative task list or wiki for a team.
5
-
6
- You can also start a web front-end allowing the repo to be viewed through the browser.
5
+ You can also start a web front-end allowing the repo to be accessed through a browser.
7
6
 
8
7
  ## Installation
9
8
 
@@ -13,58 +12,67 @@ Install the gem:
13
12
  gem install gitdocs
14
13
  ```
15
14
 
16
- If you have Growl installed, you'll probably want to run `brew install growlnotify` to enable Growl support.
15
+ If you have Growl installed on Max OSX, you'll probably want to run:
16
+
17
+ ```
18
+ brew install growlnotify
19
+ ```
20
+
21
+ to enable Growl support (other platforms coming soon).
17
22
 
18
23
  ## Usage
19
24
 
20
- First add the doc folders to watch:
25
+ Gitdocs is centered around 'watching' any number of directories for changes and keeping them automatically synced. You can either add
26
+ existing git directories for monitoring or have gitdocs pull down a repository to monitor.
27
+
28
+ You can add existing folders to watch:
21
29
 
22
30
  ```
23
31
  gitdocs add my/path/to/watch
24
32
  ```
25
33
 
26
- You can remove and clear paths as well:
34
+ or instruct gitdocs to fetch a remote repository and keep it synced with:
27
35
 
28
36
  ```
29
- gitdocs rm my/path/to/watch
30
- # or gitdocs clear
37
+ gitdocs create local/path/for/repo git@github.com:user/some/remote/repo.git
31
38
  ```
32
39
 
33
- You need to startup gitdocs:
40
+ This will clone the remote repo and begin monitoring the local path. You can remove and clear monitored paths as well:
34
41
 
35
42
  ```
36
- gitdocs start
43
+ gitdocs rm my/path/to/watch
44
+ gitdocs clear
37
45
  ```
38
46
 
39
- If the start command doesn't seem to properly start the process, you can run with a debug flag:
47
+ You need to start gitdocs in order for the monitoring to work:
40
48
 
41
49
  ```
42
- gitdocs start -D
50
+ gitdocs start
43
51
  ```
44
52
 
45
- You can also `stop` and `restart` gitdocs as needed. Run
53
+ If the start command fails, you can run again with a debug flag:
46
54
 
47
55
  ```
48
- gitdocs status
56
+ gitdocs start -D
49
57
  ```
50
58
 
51
- for a helpful listing of the current state. Once gitdocs is started, simply start editing or adding files to your
52
- designated git repository. Changes will be automatically pushed and pulled to your local repo.
53
-
54
- You can also have gitdocs fetch a remote repository with:
59
+ and gitdocs can be easily stopped and restarted:
55
60
 
56
61
  ```
57
- gitdocs create my/path/for/doc git@github.com:user/some_docs.git
62
+ gitdocs stop
63
+ gitdocs restart
58
64
  ```
59
65
 
60
- This will clone the repo and add the path to your watched docs. Be sure to restart gitdocs
61
- to have path changes update:
66
+ For an overview of gitdocs current status, run:
62
67
 
63
68
  ```
64
- gitdocs restart
69
+ gitdocs status
65
70
  ```
66
71
 
67
- To view the docs in your browser with file formatting:
72
+ Once gitdocs has been started and is monitoring the correct directories, simply start editing or adding files to your
73
+ designated git repos. Changes will be automatically pushed and pulled to your local repos.
74
+
75
+ To explore the repos in your browser, simply start the server:
68
76
 
69
77
  ```
70
78
  gitdocs serve
@@ -74,8 +82,23 @@ and then visit `http://localhost:8888` for access to all your docs in the browse
74
82
 
75
83
  ## Planned Features
76
84
 
77
- - A web UI for uploading, and editing text files (in addition to viewing)
78
- - Local-area peer-to-peer sync.
79
- - Click-to-share instant access granting.
80
- - Better conflict-resolution behavior (maintains both versions of a file)
81
- - Support for linux and windows (coming soon)
85
+ Gitdocs is a young project but we have big plans for it including:
86
+
87
+ - A web front-end UI for file uploading and editing of files (with rich text editor and syntax highlighting)
88
+ - Local-area peer-to-peer syncing, avoid 'polling' in cases where we can using a messaging protocol.
89
+ - Click-to-share instant access granting file access to users using a local tunnel or other means.
90
+ - Better conflict-resolution behavior on updates (maintain both versions of a file)
91
+ - Support for linux and windows platforms (coming soon), and maybe android and iOS as well?
92
+
93
+ ## Prior Projects
94
+
95
+ Gitdocs is a fresh project that we spiked on in a few days time. Our primary goals are to keep the code as simple as possible,
96
+ but provide the features that makes dropbox great. If you are interested in other Dropbox alternatives, be sure to checkout our notes below:
97
+
98
+ * [SparkleShare](http://sparkleshare.org/) is an open source, self-hosted Dropbox alternative. Nice project and a great alternative but has a lot of dependencies,
99
+ more complex codebase, and lacks some of the features we have planned for gitdocs in the near future.
100
+ * [DVCS-Autosync](http://mayrhofer.eu.org/dvcs-autosync) is a project to create an open source replacement for Dropbox based on distributed version control systems.
101
+ Very similar project but again we have features planned that are out of scope (local tunnel file sharing, complete web ui for browsing, uploading and editing).
102
+ * [Lipsync](https://github.com/philcryer/lipsync) is another similar project. We haven't looked at this too closely, but thought we would mention it in this list.
103
+
104
+ If any other open-source dropbox alternatives are available, we would love to hear about them so let us know!
@@ -134,8 +134,8 @@ module Gitdocs
134
134
  def sh_with_code(cmd)
135
135
  cmd << " 2>&1"
136
136
  outbuf = ''
137
- outbuf = `cd #{@root} && #{cmd}`
137
+ outbuf = `cd "#{@root}" && #{cmd}`
138
138
  [outbuf, $?]
139
139
  end
140
140
  end
141
- end
141
+ end
@@ -1,3 +1,3 @@
1
1
  module Gitdocs
2
- VERSION = "0.1.4"
2
+ VERSION = "0.1.5"
3
3
  end
metadata CHANGED
@@ -2,7 +2,7 @@
2
2
  name: gitdocs
3
3
  version: !ruby/object:Gem::Version
4
4
  prerelease:
5
- version: 0.1.4
5
+ version: 0.1.5
6
6
  platform: ruby
7
7
  authors:
8
8
  - Josh Hull
@@ -11,7 +11,7 @@ autorequire:
11
11
  bindir: bin
12
12
  cert_chain: []
13
13
 
14
- date: 2011-11-30 00:00:00 -08:00
14
+ date: 2011-12-01 00:00:00 -08:00
15
15
  default_executable:
16
16
  dependencies:
17
17
  - !ruby/object:Gem::Dependency
@@ -159,6 +159,7 @@ extra_rdoc_files: []
159
159
  files:
160
160
  - .gitignore
161
161
  - Gemfile
162
+ - LICENSE
162
163
  - README.md
163
164
  - Rakefile
164
165
  - bin/gitdocs