mirror of https://github.com/perkeep/perkeep.git
90042fe296
vendor: add github.com/aws/aws-sdk-go at rev bc3f534c19ffdf835e524e11f0f825b3eaf541c3 This changes all uses of the s3 client to be the official aws-sdk-go. As such, it also deletes the previous client maintained in internal. There are a few notable changes that come with this: 1. An 'aws_region' key is added to the low-level config. The 'get-bucket-location' call is used to identify the correct region rather than using the redirect returned to determine it. 2. Deleting multiple objects at once is much faster (batches of up to 1000 vs 1 at a time). 3. Retriable errors are retried automatically (see #1184). 4. Newer APIs are used for some operations (v2 / batch apis). An unfortunate result of 4 is that this is technically a backwards incompatible change. An IAM policy which used to be sufficient for perkeep may no longer permit some of the new api calls (even if they're not doing anything different really). Fixes #1184, #911 Change-Id: I077fe88def18b7e9a14267820773245e7003634c |
||
|---|---|---|
| .. | ||
| example-blobs | ||
| json-signing | ||
| protocol | ||
| publishing | ||
| release | ||
| schema | ||
| todo | ||
| README.md | ||
| app-environment.md | ||
| arch.md | ||
| client-config.md | ||
| compare.md | ||
| environment-vars.md | ||
| geocoding.md | ||
| overview.md | ||
| overview.txt | ||
| principles.md | ||
| prior-art.md | ||
| release.txt | ||
| search-ui.md | ||
| server-config.md | ||
| sharing.md | ||
| status.md | ||
| storage-examples.md | ||
| synology.md | ||
| terms.md | ||
| uses.md | ||
| web-ui-styleguide.md | ||
README.md
Documentation
- Overview: The original motivation and background for why Perkeep exists and what one might use it for.
- Compare: how Perkeep compares to similar services and software
For Users
If you're just looking to set up a Perkeep 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 Perkeep servers or backup to cloud storage providers
- Client config: Clients need this configuration file to securely connect to your Perkeep server(s)
- Search Commands: Covers the available search operators
- Configuring Geocoding: how to enable geocoding (the
loc:search operator)
For Developers
If you want to help the development of Perkeep or just want to know more about the how and why behind Perkeep, these docs are going to help you get started. Something we didn't cover here that you're interested in? Ask on the mailing list.
Concepts
- Principles: our base principles, goals, assumptions
- Terminology: let's agree on terms to stay sane
- Use Cases: what one might do with all this (or at least our aspirations)
- Prior Art: other projects with similar goals or strategies
- Contributing: how to help
- Style guide for the Web UI
Technical Docs
- Packages: internal API documentation
- Architecture: the pieces, layers, and how they interact
- Schema: how we model data in Perkeep
- Protocol: HTTP APIs (discovery, blob storage, JSON signing, ...)
- JSON Signing
- Sharing
Presentations
- 2018-04, LinuxFest Northwest: [slides] [video]
- 2016-04, GDG Seattle: [slides] [video]
- 2016-04, LinuxFest Northwest: [slides] [video]
- 2015-02, FOSDEM: [slides] [video]
- 2014-02, FOSDEM: [slides] [video] [WebM]
- 2013-06, Google Developers Live: [video]
- 2011-05, São Paolo Perl Conference: [slides]
- 2011-02, First Introduction: [slides]