summaryrefslogtreecommitdiff
path: root/_posts/2011-04-11-blogrite-git-or-dropbox.html
blob: 7a241d2c8815de4e8e1eccd23434aca696c14b89 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
---
layout: post
title: Blogrite - Git or Dropbox?
tags:
- Miscellaneous
- ruby
- screencast
status: publish
type: post
published: true
meta:
  _wp_old_slug: blogrite-%e2%80%94-git-or-dropbox
  _edit_last: '1'
---
The absence of communication has been resounding for a while. I have been thinking about Blogrite, nonetheless. I want to show something in the local Ruby meetup next month.
<h3>The million dollar question</h3>
Today I went to #git in Freenode, asking for how should I learn git in order to use it as a filesystem and access it remotely via some server using Grit. The somehow arrogant yet most likely right answer I got was: <em>don't</em>. Well, what should I use then? The same guy didn't answer me (well, he did: "<em>I don't know".</em>) but another guy did.
<blockquote>Why not use Dropbox or Amazon S3?</blockquote>
Actually that is a great idea. Again, my principle is: keep it minimal and lightweight and still easy for geeks to use. Dropbox is definitely easy to use and maintain. You can also version the content with Git; it just won't be part of my engine.
<h3>The million dollar answer</h3>
I will use Dropbox as the content database. Git will have to wait. It shall come, but not just yet. This gives me opportunity to create modular adapters later on so I feel confortable with it.