With using a VCS back end you are creating an interesting scenario. Now either your first tier, the web server, needs to know about your VCS client and sync up on command or automatically or you push changes yourself. While offering revision control, this isn't beyond the realm of a common LAMP stack either. Even Drupal can be setup to track revisions to articles.<div>
<br></div><div>One of the reasons I like a DB backed page is that content is just content. You can easily pull in bits and pieces as needed. There is no need to combine it all into a final product before publishing to the public. Of course this seriously ups complexity. </div>
<div><br></div><div>As for VCS, I guess I just don't envision a middle tier existing in this scenario at all. Your web service just provides static pages at this point. </div><div><br></div><div>In anycase, I'll keep my eyes open on this subject, I enjoy watching a new paradigm unfold in this space. </div>
<div><br></div><div>Dan</div><div><br><div class="gmail_quote">On Wed, May 23, 2012 at 10:57 PM, David L. Anselmi <span dir="ltr"><<a href="mailto:anselmi@anselmi.us" target="_blank">anselmi@anselmi.us</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">Jim Ockers wrote:<br>
> Couldn't you use an instance Joomla on your Linux box for your blog? It's not exactly easy peasy but<br>
> once you get the hang of it, it works great...<br>
<br>
</div>I could but:<br>
<br>
- PHP<br>
- MySQL<br>
- not git<br>
<br>
To me a VCS seems like a much better back end than a RDBMS for a blog/wiki. There are plenty of<br>
examples that are functional and attractive. Versioning is to me a necessary feature. Although a<br>
DB might make sense for relating comments/attachments/stuff it seems easier to add that to a VCS<br>
than to build a VCS in a DB.<br>
<br>
For what I think of in blog/wiki, LAMP and CMS are so much overkill.<br>
<br>
I didn't mention that I probably won't use Apache, but I probably won't. (I do need to think about<br>
a non-tech user friendly wiki, which might not be ikiwiki, and therefor might require Apache. But<br>
I'm going to try to avoid that.)<br>
<div class="HOEnZb"><div class="h5"><br>
Dave<br>
_______________________________________________<br>
clue mailing list: <a href="mailto:clue@cluedenver.org">clue@cluedenver.org</a><br>
For information, account preferences, or to unsubscribe see:<br>
<a href="http://cluedenver.org/mailman/listinfo/clue" target="_blank">http://cluedenver.org/mailman/listinfo/clue</a><br>
</div></div></blockquote></div><br></div>