From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by arlo.cworth.org (Postfix) with ESMTP id 50D8D6DE0927 for ; Sun, 13 Jan 2019 10:12:44 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -0.001 X-Spam-Level: X-Spam-Status: No, score=-0.001 tagged_above=-999 required=5 tests=[AWL=-0.000, DKIMWL_WL_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=disabled Received: from arlo.cworth.org ([127.0.0.1]) by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1fn7IEaqzK08 for ; Sun, 13 Jan 2019 10:12:43 -0800 (PST) Received: from mail-wr1-f41.google.com (mail-wr1-f41.google.com [209.85.221.41]) by arlo.cworth.org (Postfix) with ESMTPS id 333626DE0924 for ; Sun, 13 Jan 2019 10:12:43 -0800 (PST) Received: by mail-wr1-f41.google.com with SMTP id l9so20370178wrt.13 for ; Sun, 13 Jan 2019 10:12:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=adirat-com.20150623.gappssmtp.com; s=20150623; h=from:to:subject:in-reply-to:references:date:message-id:mime-version :content-transfer-encoding; bh=/FAPwJJUqsjG4n7tMbJO+HrDudgLt8YGr8vmYXyPCj4=; b=RwDMNHnEGbmeeIXFLdDis6FHtKDpqWzK8GPzX3hnytSx5EFfODu9c4d3aUWQnBIWcQ rq+MeScuGBeJ8flSNGAv1t2C7lw1H8BerPjKiUXITd6NjRFJxZ5bDVQSmoD+I/HW74Bw k4243AY0HRvbEIMGjy2JPlHOYHsitZogLzHLpsICVvReChcsEQLcB+oQHQneaYIb9OZ8 BJF4ryDyeiopbYykKy/Xwtt0I1FJNHQPIV4Zg42YKcJ7vi5N4Y9azd52J6tw/ie6OLoF qjGkn93kjfRB3HF+xnsrBuz/R0VXfkIhPQo1r33bnOIvUhFaQGwO+e0aajCKQvcllghC ZXkQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:in-reply-to:references:date :message-id:mime-version:content-transfer-encoding; bh=/FAPwJJUqsjG4n7tMbJO+HrDudgLt8YGr8vmYXyPCj4=; b=TVKlRqjnAyg7XfadjWbG6nwBoJ0U1hHWFdvRT2Dn6OkXZJyB4tWLuC1+QSeFGVGqqb scNEyQ+aFQ4iHH/68EnuK+UrxrCgCI71XguCxfbwG8Ap8YmnpaInSmsvBTIFOYlMX5Cm yeSdg3Q7rJ4YS5rkZA4KZOfshwGkzZLoS40VHGdU6WQlaeVENX4fFR4fadJjcqNyNFUi NWl9Y9ic3suQDIvRl3cnnN1LWWZaVWsTNsIvybg6f1GBMKGRAGkZC0XZJLIZYDpauZcc 1hLZrCgJjUZR6bMwZP/yhOI26G/nlbQmCwuVRQ6sXiOg4PXTf8GNNtDcNRAv8A6dG6a3 xHNw== X-Gm-Message-State: AJcUukdc3m/bf1lw/+Fdgysx2J9ri9aAHhAzqlb8XPqIwdYbpQcM16uz wlMKDSCLH4kqAJfjQcv0EB8fPo6TflWHfQ== X-Google-Smtp-Source: ALg8bN4Gh/OER+x9KMJmI25j6xnjztjNZ/0gxOxc08b95K8Eoz/gI/Cn2jUlx6otQdHZwRVj9QcX0Q== X-Received: by 2002:a5d:4652:: with SMTP id j18mr21855341wrs.279.1547403160227; Sun, 13 Jan 2019 10:12:40 -0800 (PST) Received: from adiPC ([188.24.59.111]) by smtp.gmail.com with ESMTPSA id q12sm18857372wmf.2.2019.01.13.10.12.39 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sun, 13 Jan 2019 10:12:39 -0800 (PST) From: Ioan-Adrian Ratiu To: Dan =?utf-8?B?xIxlcm3DoWs=?= , notmuch@notmuchmail.org Subject: Re: How do you synchronize your notmuch tags across multiple machines? In-Reply-To: <87d0pzwykt.fsf@cgc-instruments.com> References: <87d0pzwykt.fsf@cgc-instruments.com> Date: Sun, 13 Jan 2019 20:12:43 +0200 Message-ID: <87sgxwbf50.fsf@adiPC.i-did-not-set--mail-host-address--so-tickle-me> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jan 2019 18:12:44 -0000 My solution to this problem is to have only one notmuch instance=20 run on a remote VPS and connect to it via "thin" notmuch-emacs=20 front-ends, very similar to [1]. It has been working very well for=20 the last few years. [1] https://notmuchmail.org/remoteusage/ On Mon, 17 Dec 2018, Dan =C4=8Cerm=C3=A1k wrote: > Hi list, > > first and foremost: thanks to everyone who contributed to notmuch, it's > a truly awesome piece of software. > > Unfortunately, I am facing the problem (which I have been postponing to > face for a while) that I'll need to keep my notmuch database in sync > over multiple machines. > Thus my question: how are you achieving that? How well does your > solution work? > > (I have found muchsync, but unfortunately very little reports about how > well it works, which isn't necessarily a bad thing. Beside that only > some scripts around notmuch dump.) > > > Thanks in advance, > > Dan > _______________________________________________ > notmuch mailing list > notmuch@notmuchmail.org > https://notmuchmail.org/mailman/listinfo/notmuch