From 3204575bfcd1f12db5945c8959073d40915cfdfe Mon Sep 17 00:00:00 2001 From: JoseĢ Mota Date: Fri, 6 Apr 2012 19:40:37 +0100 Subject: Import all posts. --- _posts/2011-04-11-blogrite-git-or-dropbox.html | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) create mode 100644 _posts/2011-04-11-blogrite-git-or-dropbox.html (limited to '_posts/2011-04-11-blogrite-git-or-dropbox.html') diff --git a/_posts/2011-04-11-blogrite-git-or-dropbox.html b/_posts/2011-04-11-blogrite-git-or-dropbox.html new file mode 100644 index 0000000..7a241d2 --- /dev/null +++ b/_posts/2011-04-11-blogrite-git-or-dropbox.html @@ -0,0 +1,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. +

The million dollar question

+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: don't. Well, what should I use then? The same guy didn't answer me (well, he did: "I don't know".) but another guy did. +
Why not use Dropbox or Amazon S3?
+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. +

The million dollar answer

+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. -- cgit v1.2.3-54-g00ecf