unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Matthew Lear <matt@bubblegen.co.uk>
To: notmuch@notmuchmail.org
Subject: web interface to notmuch
Date: Thu, 19 Oct 2017 15:43:54 +0100	[thread overview]
Message-ID: <CAJFxaw-_OFGE-t1dz6Mwa+5o6Hzes5SJVwYSX5xJ44XNCXxcwA@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1774 bytes --]

Hello all. A little side project at work involves me trying to put together
part of a knowledge share system where users can query and search email
stored and indexed centrally (by offlineimap & notmuch). My intention is to
provide a means to support multiple concurrent read-only accesses to the
notmuch database from users' web browsers so they can query and search mail.

Consider a few different email addresses being plugged into various
systems, all receiving email on different topics. I'd like to build an
application which presents a web frontend which I can run on the server
which fetches and indexes the mail, and thus present a web interface to
search all mail using notmuch.

notmuch-web has not seen much development for a few years.
noservice looks pretty nifty but I'm a little unsure of the status and if
it's missing anything fundamental.

I think my requirements are pretty basic:

* Read-only access
* Search and display mail only (no sending), including html mails
* Freeform entry of search terms in accordance with notmuch-search-terms(7).

Would anybody have any ideas about the best way to undertake such a project?

notmuch-web and noservice definitively look like they could be leveraged,
but I don't know if I'd be better trying to construct something from the
ground up which is better suited / tailored to my requirements (which are
much less than either of the above were intended to fulfil).

A standalone app would be preferred rather than having to rely on a web
server, although I'm not picky about infrastructure. Web based programming
is not my forte so I'd appreciate any feedback relating also to
implementation, currently available open source web frameworks which could
be used / considered / leveraged, etc.

Many thanks,
--  Matt

[-- Attachment #2: Type: text/html, Size: 2080 bytes --]

             reply	other threads:[~2017-10-19 14:51 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-19 14:43 Matthew Lear [this message]
2017-10-19 15:01 ` web interface to notmuch Brian Sniffen
2017-10-19 16:55   ` Daniel Kahn Gillmor
2017-10-19 20:00     ` Brian Sniffen
2017-10-19 20:13       ` Daniel Kahn Gillmor
2017-10-21 20:00     ` Jani Nikula
2017-10-21 22:21       ` Daniel Kahn Gillmor
2017-10-24 12:39         ` Vladimir Panteleev
     [not found]         ` <27e53def-32b4-45ab-1192-77cc0e837a93@gmail.com>
2017-10-24 20:03           ` Matthew Lear
2017-10-25 22:03           ` Brian Sniffen
2017-10-26 21:25             ` Daniel Kahn Gillmor
2017-10-27  4:04               ` Brian Sniffen
2017-10-27  4:24                 ` Daniel Kahn Gillmor
2017-10-27 10:02                   ` Matthew Lear
2017-10-27  6:05                 ` Daniel Kahn Gillmor
2017-10-27 17:52                   ` Brian Sniffen
2017-10-31 17:13                     ` Matthew Lear
2017-10-31 18:47                       ` Tomas Nordin
2017-10-31 19:21                       ` Brian Sniffen
2017-10-31 21:32                         ` Matthew Lear
2017-11-01 13:01                           ` Matthew Lear
2017-11-01 14:38                           ` Brian Sniffen
2017-11-02 17:32                             ` Matthew Lear
2017-12-06 15:00     ` Brian Sniffen
2017-12-06 19:13       ` Daniel Kahn Gillmor
2017-12-07  1:00       ` David Bremner
2017-10-20 19:25 ` W. Trevor King

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://notmuchmail.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAJFxaw-_OFGE-t1dz6Mwa+5o6Hzes5SJVwYSX5xJ44XNCXxcwA@mail.gmail.com \
    --to=matt@bubblegen.co.uk \
    --cc=notmuch@notmuchmail.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://yhetil.org/notmuch.git/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).