website: update uses

Change-Id: I06097eea55e7af394b299205bc404723b1eaf6a4
This commit is contained in:
Brad Fitzpatrick 2013-06-12 16:08:56 -07:00
parent a9bfb22147
commit 87e38b5023
1 changed files with 4 additions and 4 deletions

View File

@ -1,9 +1,10 @@
<h1>Use Cases</h1>
<p>Camlistore is currently more of a vision than a product, but let us
at least lay out some of that vision here.</p>
<p>First, read <a href="/docs/overview">the overview</a>.</p>
<p>What could one potentially do with all this?</p>
<p>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).</p>
<ul class='lispaced'>
<li><b>Filesystem backups</b>: easy initial use case. Since you can easily put <a href="/docs/schema">files & directories and such</a> in camlistore with <a href="/cmd/camput">camput</a>, you can use Camlistore for your backups. Incremental backups are basically free.</li>
@ -18,5 +19,4 @@ at least lay out some of that vision here.</p>
<li><b>Import/export adapters for hosted web services:</b> 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.</li>
</ul>