Rooba
/
perkeep
mirror of https://github.com/perkeep/perkeep.git
1
1
Fork 0
Code Issues Packages Projects Releases Wiki Activity
perkeep/doc/uses.md

39 lines
1.8 KiB
Markdown
Raw Normal View History

website: convert docs pages to markdown This includes all of the top-level files in the docs folder except for status and terms, which are going to be a little trickier to convert. This includes no editorial changes. There are a few minor stylistic changes (like the auth value table in server-config converted into a list). Text has also been mostly wrapped at 80 columns, which accounts for a lot of the changes as well. Change-Id: I3782158f05d2b3c72e6cb44bff92c46ccc231a96
2015-07-26 21:32:30 +00:00
# Use Cases
website: fix remaining old links to /docs/ interestingly, I also discovered that GitHub will properly resolve links that are relative to the root path (e.g. "/doc/foo")... it properly rewrites these links to reference the named file relative to the repository root. also add a /doc/contributing.md file. This will never be served from the website, since we have a redirect handler in place, but is added so that we don't have broken links when browsing the docs on GitHub. Change-Id: I47517a5f6303065df02ac11771dcee56cd06a4b7
2016-05-02 05:20:16 +00:00
First, read [the overview](/doc/overview.md).
website: convert docs pages to markdown This includes all of the top-level files in the docs folder except for status and terms, which are going to be a little trickier to convert. This includes no editorial changes. There are a few minor stylistic changes (like the auth value table in server-config converted into a list). Text has also been mostly wrapped at 80 columns, which accounts for a lot of the changes as well. Change-Id: I3782158f05d2b3c72e6cb44bff92c46ccc231a96
2015-07-26 21:32:30 +00:00
These are some higher-level roadmap goals. Only the first few are done, but all
are various stages of implementation (as of 2013-06-12).
* **Filesystem backups**: easy initial use case. Since you can easily put
website: fix remaining old links to /docs/ interestingly, I also discovered that GitHub will properly resolve links that are relative to the root path (e.g. "/doc/foo")... it properly rewrites these links to reference the named file relative to the repository root. also add a /doc/contributing.md file. This will never be served from the website, since we have a redirect handler in place, but is added so that we don't have broken links when browsing the docs on GitHub. Change-Id: I47517a5f6303065df02ac11771dcee56cd06a4b7
2016-05-02 05:20:16 +00:00
[files & directories and such](/doc/schema/) in camlistore with
website: convert docs pages to markdown This includes all of the top-level files in the docs folder except for status and terms, which are going to be a little trickier to convert. This includes no editorial changes. There are a few minor stylistic changes (like the auth value table in server-config converted into a list). Text has also been mostly wrapped at 80 columns, which accounts for a lot of the changes as well. Change-Id: I3782158f05d2b3c72e6cb44bff92c46ccc231a96
2015-07-26 21:32:30 +00:00
[camput](/cmd/camput), you can use Camlistore for your backups. Incremental
backups are basically free.
* **Efficient remote filesystem**: should be easy to do an aggressively caching
remote FUSE filesystem. Read-only is trivial. Read-write shouldn't be too
painful. Every modification would be snapshotted implicitly, so revision
control would be the default.
* **Decentralized sharing system**: share anything of yours with anybody or
everybody (private is the default). This is already starting to work. See
website: fix remaining old links to /docs/ interestingly, I also discovered that GitHub will properly resolve links that are relative to the root path (e.g. "/doc/foo")... it properly rewrites these links to reference the named file relative to the repository root. also add a /doc/contributing.md file. This will never be served from the website, since we have a redirect handler in place, but is added so that we don't have broken links when browsing the docs on GitHub. Change-Id: I47517a5f6303065df02ac11771dcee56cd06a4b7
2016-05-02 05:20:16 +00:00
[sharing](/doc/sharing.md).
website: convert docs pages to markdown This includes all of the top-level files in the docs folder except for status and terms, which are going to be a little trickier to convert. This includes no editorial changes. There are a few minor stylistic changes (like the auth value table in server-config converted into a list). Text has also been mostly wrapped at 80 columns, which accounts for a lot of the changes as well. Change-Id: I3782158f05d2b3c72e6cb44bff92c46ccc231a96
2015-07-26 21:32:30 +00:00
* **Blog / photo hosting / Document Management CMS:** I intend to run my
personal blog and photo / gallery hosting (with permissions) off of Camlistore.
I also intend to replace my "scanningcabinet" document management software and
use Camlistore instead.
* **Decentralized social networking**: a lofty but persistent goal. For
example, to implement comments or tagging: One person could use claims to
attach metadata to another person's image blob. The signing lets you verify
identity. The sharing/syncing semantics of camlistore let you easily save a
copy of all your friends' pictures.
* **Import/export adapters for hosted web services:** Don't worry about web
services shutting down or going downhill. Mirror all your data online in your
private store. Create it either in Camlistore (using open tools) and export to
hosted services, or create content in hosted services and continually mirror it
back into your private Camlistore. Relax knowing that your data is yours,
forever.