couchdb-marketing mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jan Lehnardt <...@apache.org>
Subject Re: Drupal + CouchDB
Date Tue, 29 Mar 2016 14:16:14 GMT
Tim,

this is brilliant!

If nobody objects, I’ll post this later today.

Jenn, we want to add this to the weekly news ;)

Best
Jan
--

> On 26 Mar 2016, at 11:34, Tim Millwood <tim@millwoodonline.co.uk> wrote:
> 
> For those who have access I have provided an initial draft of my blog post
> at https://couchdbblog.wordpress.com/?p=937&preview=true
> 
> I will be proof reading and reviewing through today with an aim to publish
> later in the week.
> 
> All feedback welcome.
> 
> I tried to keep it pretty high level and not too technical, and would be
> happy to provide follow up posts with more technical details if there's
> interest.
> 
> On 22 March 2016 at 13:37, Jan Lehnardt <jan@apache.org> wrote:
> 
>> Oops, sorry, I left you hanging there. I’ve now added you as an author to
>> blog.couchdb.org.
>> 
>> Best
>> Jan
>> --
>> 
>>> On 22 Mar 2016, at 13:24, Tim Millwood <tim@millwoodonline.co.uk> wrote:
>>> 
>>> I've setup a wordpress account, username "timmillwood1".
>>> 
>>> On 22 March 2016 at 12:19, Garren Smith <garren@apache.org> wrote:
>>> 
>>>> Sorry I'm really slow to reply on this. This is really great Tim. I'm
>>>> looking forward to the blogpost.
>>>> 
>>>> On Thu, Mar 17, 2016 at 11:30 AM, Andy Wenk <andywenk@apache.org>
>> wrote:
>>>> 
>>>>> This is all awesome - thanks a lot Tim ;-)
>>>>> 
>>>>> If you need a reviewer for the blog post, I am happy to do so.
>>>>> 
>>>>> All the best
>>>>> 
>>>>> Andy
>>>>> --
>>>>> Andy Wenk
>>>>> Hamburg - Germany
>>>>> RockIt!
>>>>> 
>>>>> GPG public key:
>>>>> https://pgp.mit.edu/pks/lookup?op=get&search=0x4F1D0C59BC90917D
>>>>> 
>>>>> 
>>>>>> On 16 Mar 2016, at 19:40, Jan Lehnardt <jan@apache.org> wrote:
>>>>>> 
>>>>>> Heya Tim,
>>>>>> 
>>>>>> thanks for writing! :)
>>>>>> 
>>>>>> I hope everyone agrees here that what you are doing is amazing and
we
>>>>>> wish you the best of luck.
>>>>>> 
>>>>>> But we also want to help with highlighting your work and showing
the
>>>>>> world what is possible.
>>>>>> 
>>>>>> I think your outline looks like a great outline for a blog post
>>>> already,
>>>>>> so unless anyone here objects, feel free to write up a draft at any
>>>> time
>>>>>> and we’ll take it from there.
>>>>>> 
>>>>>> If you want to sign up for an account on http://blog.couchdb.org
then
>>>>>> I can add you to the editorial team and you can write the draft right
>>>>>> in WordPress where we publish these things, just tell me your username
>>>> :)
>>>>>> 
>>>>>> Looking forward to reviewing your draft!
>>>>>> 
>>>>>> Best
>>>>>> Jan
>>>>>> --
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>>> On 16 Mar 2016, at 13:31, Tim Millwood <tim@millwoodonline.co.uk>
>>>>> wrote:
>>>>>>> 
>>>>>>> After debugging some issues on IRC with Jan he invited me to
propose
>>>> an
>>>>>>> article for the CouchDB blog about the work I'm doing for Drupal
and
>>>>>>> CouchDB.
>>>>>>> 
>>>>>>> For those that haven't seen, the TL;DR is: We are exposing CouchDB
>>>>>>> compatible endpoints from Drupal (the PHP based CMS, you knew
that,
>>>>>>> right?), so that we can replicate content between Drupal sites
using
>>>> the
>>>>>>> replication.io protocol.
>>>>>>> 
>>>>>>> It'd be awesome to write a blog post giving a wide arching overview
>> of
>>>>> what
>>>>>>> we are doing. We've had to:
>>>>>>> - Alter all content in Drupal to be revisionable and enforce
that
>>>>>>> - Implement revision hashes
>>>>>>> - Prevent revisions from being deleted (and add _deleted flag)
>>>>>>> - Store parent revisions and generate a revision tree
>>>>>>> - Normalize and denormalize all content to and from json
>>>>>>> - Setup all endpoints
>>>>>>> - Implement a replicator in php so we can do full Drupal to Drupal
>>>>>>> replication without CouchDB
>>>>>>> 
>>>>>>> One link I shared with Jan was
>>>>>>> https://travis-ci.org/relaxedws/drupal-relaxed/jobs/116109952
which
>>>>> shows a
>>>>>>> test we run adding documents to couchdb, then using out PHP
>> replicator
>>>>> to
>>>>>>> replicate these documents from couchdb, to drupal, then to another
>>>>> drupal
>>>>>>> site, then back to couchdb again. We can a number of additional
>>>>> documents
>>>>>>> through the process, but these are Drupal uses which we are treating
>>>> as
>>>>>>> documents and also replicating.
>>>>>> 
>>>>>> --
>>>>>> Professional Support for Apache CouchDB:
>>>>>> https://neighbourhood.ie/couchdb-support/
>>>>>> 
>>>>> 
>>>>> 
>>>> 
>> 
>> --
>> Professional Support for Apache CouchDB:
>> https://neighbourhood.ie/couchdb-support/
>> 
>> 

-- 
Professional Support for Apache CouchDB:
https://neighbourhood.ie/couchdb-support/


Mime
View raw message