On Jun 6, 12:33 am, Marnen Laibow-Koser <[email protected]> wrote:
> Ginty wrote:
> > On Jun 3, 9:58 pm, Marnen Laibow-Koser <[email protected]> wrote:
> >> Real user accounts in your repository. Even with one person and
> >> Capistrano, that's two users, and they should have separate Git repo
> >> accounts.
>
> >> Also, can you push to a Git repo on Dropbox? If not, then it's not a
> >> good Git hosting solution -- and of course it doesn't speak the Git
> >> protocol.
>
> > Of course, you interface to dropbox via a regular dir on your local
> > machine, push, pull, anything else you can do locally. In the
> > background the Dropbox client takes the updates away into the cloud
> > and mirrors them to all of your other machines.
>
> In other words, you're not using the remote copy as a Git repo -- you're
> not pushing directly to it from your local machine?  If that's the case,
> it's a huge disadvantage of Dropbox.
>
> Set up a Github account and try pushing to it.  You'll see the
> difference.
>

Naw it's exactly the same workflow. Work on your local copy, push to
Dropbox, pull from wherever else you have access to your Dropbox.

>
>
> > Using it for this or not Dropbox is a truly great web app, and the
> > paid versions are actually cheaper than you would pay S3 directly for
> > the same amount of storage, plus 0 transfer charges.
>
> But that's just backup.  It sounds like it isn't appropriate for
> repository hosting.

It is.
>
>
>
> > Also thanks for the Redmine suggestion, been trying it out today,
> > great stuff!
>
> You're welcome.
>
> Best,
> --
> Marnen Laibow-Koserhttp://www.marnen.org
> [email protected]
> --
> Posted viahttp://www.ruby-forum.com/.

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Talk" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-talk?hl=en.

Reply via email to