perkeep/doc
mpl 3df678b010 pkg/server/app: proxy search requests for publisher
Some of the publisher features have moved from the server-side app to
the client-side app (the browser) thanks to gopherjs. Some of these
features imply doing some search queries against Camlistore, which
requires authentication. The server-side app receives the necessary
credentials on creation, from Camlistore. However, we can't just
communicate them to the client-side (as we do with the web UI) since the
publisher app itself does not require any auth and is supposed to be
exposed to the world.

Therefore, we need to allow some search queries to be done without
authentication.

To this end, the app handler on Camlistore now assumes a new role: it is
also a search proxy for the app. The app sends an unauthenticated search
query to the app handler (instead of directly to the search handler),
and it is the role of the app handler to verify that this query is
allowed for the app, and if yes, to forward the search to the Camlistore's
search handler.

We introduce a new mechanism to filter the search queries in the form of
a master query. Upon startup, the publisher registers, using the new
CAMLI_APP_MASTERQUERY_URL env var, a *search.SearchQuery with the app
handler. The app handler runs that query and caches all the blob refs
included in the response to that query. In the following, all incoming
search queries are run by the app handler, which checks that none of the
response blobs are out of the set defined by the aforementioned cached
blob refs. If that check fails, the search response is not forwarded to
the app/client.

The process can be improved in a subsequent CL (or patchset), with finer
grained domains, i.e. a master search query per published camliPath,
instead of one for the whole app handler.

Change-Id: I00d91ff73e0cbe78744bfae9878077dc3a8521f4
2016-08-29 19:14:19 +02:00
..
example-blobs Some example blobs 2011-02-02 13:30:01 -08:00
json-signing website: update misc docs to markdown 2016-04-26 18:10:58 -07:00
protocol convert protocol docs to markdown 2016-04-26 09:37:01 -07:00
publishing pkg/server/app: improve app handling 2016-07-04 22:21:16 +02:00
release website: feature monthly releases 2016-07-06 16:41:15 +02:00
schema doc/schema: add missing link to bytes.md 2016-05-12 00:17:24 +02:00
todo website: update misc docs to markdown 2016-04-26 18:10:58 -07:00
README.md Remove /doc/contributing.md 2016-06-03 14:42:05 -07:00
app-environment.md pkg/server/app: proxy search requests for publisher 2016-08-29 19:14:19 +02:00
arch.md website: serve /doc/ URLs from top-level doc dir 2016-04-25 22:13:09 -07:00
client-config.md website: serve /doc/ URLs from top-level doc dir 2016-04-25 22:13:09 -07:00
environment-vars.md website: update misc docs to markdown 2016-04-26 18:10:58 -07:00
overview.md website: fix remaining old links to /docs/ 2016-05-02 06:26:45 -07:00
overview.txt website: fix remaining old links to /docs/ 2016-05-02 06:26:45 -07:00
principles.md website: serve /doc/ URLs from top-level doc dir 2016-04-25 22:13:09 -07:00
prior-art.md website: fix wikipedia links on prior-art page 2016-04-27 08:11:30 -07:00
release.txt doc/release.txt: fix monthly doc 2016-05-10 15:08:13 +02:00
search-ui.md website: update misc docs to markdown 2016-04-26 18:10:58 -07:00
search-ui.txt website: restore search-ui.txt with link to new page 2016-04-26 22:28:05 -07:00
server-config.md pkg/server/app: improve app handling 2016-07-04 22:21:16 +02:00
sharing.md website: fix remaining old links to /docs/ 2016-05-02 06:26:45 -07:00
status.md website: fix remaining old links to /docs/ 2016-05-02 06:26:45 -07:00
terms.md website: fix remaining old links to /docs/ 2016-05-02 06:26:45 -07:00
uses.md website: fix remaining old links to /docs/ 2016-05-02 06:26:45 -07:00
web-ui-styleguide.md website: serve /doc/ URLs from top-level doc dir 2016-04-25 22:13:09 -07:00

README.md

Documentation

  • Overview: The original motivation and background for why Camlistore exists and what one might use it for.

For Users

If you're just looking to set up a Camlistore server and use it yourself, check out our getting started guide. The documents below go into more detail on customizing the high level configuration for use such as alternative blob storage or synchronization to cloud storage.

  • Command-line tools
  • Server Config: Details for configuring server storage and access, including synchronization to other Camlistore servers or backup to cloud storage providers
  • Client config: Clients need this configuration file to securely connect to your Camlistore server(s)

For Developers

If you want to help the development of Camlistore or just want to know more about the how and why behind Camlistore, these docs are the going to help you get started. Something we didn't cover here that you're interested in? Ask on the mailing list.

Concepts

Technical Docs

Presentations

Video tutorials