+ 
+
+
+
+ 
+
+
+ 
-[](https://travis-ci.org/eikek/docspell)
+[](https://travis-ci.org/eikek/docspell)
[](https://scala-steward.org)
-
+[](https://github.com/eikek/docspell/blob/master/LICENSE.txt)
+[](https://hub.docker.com/r/eikek0/docspell)
+[](https://gitter.im/eikek/docspell)
# Docspell
@@ -65,14 +67,14 @@ away:
``` shell
git clone https://github.com/eikek/docspell
cd docspell
-docker-compose up
+DOCSPELL_HEADER_VALUE="my-secret-123" docker-compose up
```
Then go to `http://localhost:7880`, sign up and login. Use the same
name for collective and user for now. More on that can be found
[here](https://docspell.org/docs/intro/).
-There are other ways, documented
+Other ways are documented
[here](https://docspell.org/docs/install/quickstart/):
- Install the [provided](https://github.com/eikek/docspell/releases)
diff --git a/website/elm/GetStarted.elm b/website/elm/GetStarted.elm
index c3c356dc..13c7314f 100644
--- a/website/elm/GetStarted.elm
+++ b/website/elm/GetStarted.elm
@@ -62,6 +62,12 @@ The directory contains a file `docspell.conf` that you can
]
, ul []
[ li []
+ [ text "Find out "
+ , a [ href "/docs/feed" ]
+ [ text "how files can get into Docspell."
+ ]
+ ]
+ , li []
[ text "The "
, a [ href "/docs/intro" ]
[ text "introduction" ]
diff --git a/website/site/content/docs/feed/_index.md b/website/site/content/docs/feed/_index.md
new file mode 100644
index 00000000..2187a2d4
--- /dev/null
+++ b/website/site/content/docs/feed/_index.md
@@ -0,0 +1,128 @@
++++
+title = "Feed Data into Docspell"
+weight = 5
+description = "Shows several ways for getting data into Docspell."
+insert_anchor_links = "right"
+[extra]
+mktoc = true
++++
+
+One of the main goals is to stow documents away quickly.
+
+Docspell makes no assumptions about where your documents are. It
+offers just one HTTP endpoint that accepts files. (Well, technically
+you create them in the webapp, and you can create many of them.) This
+endpoint is designed to work conveniently with tools like
+[curl](https://curl.haxx.se/) and it should be easy to use from other
+languages, too.
+
+So the idea is to have most flexibility – that is, it is up to you how
+documents arrive. Of course, there is something prepared:
+
+
+# Upload in Webapp
+
+This is the simplest way, but also the least flexible. You can just
+login and go to the upload page to submit files.
+
+
+{{ figure(file="web-upload.png") }}
+
+This requires to login at the webapp. Since this is complicated from
+other applications, you can create custom hard-to-guess endpoints to
+use with the following options.
+
+# Scanners
+
+If you have a (document) scanner (or think about getting one), it can
+usually be configured to place scanned documents as image or PDF files
+on your NAS. On your NAS, run the provided `consumedir.sh` script as a
+service (there is a docker container to get started) that watches this
+directory and uploads all incoming files to Docspell. The script can
+watch directories recursively and can skip files already uploaded, so
+you can organize the files as you want in there (rename, move etc).
+
+The scanner should support 300dpi for better results. Docspell
+converts the files into PDF adding a text layer of image-only files.
+
+{{ buttonright(classes="is-primary ", href="/docs/tools/consumedir", text="More") }}
+
+
+# Android
+
+There is an android client provided that lets you upload files from
+your android devices. The idea is to use a separate app, like
+[OpenNoteScanner](https://github.com/ctodobom/OpenNoteScanner), to
+"scan" documents using your phone/tablet and then upload it to
+Docspell. For the upload part, you can use the provided app. It hooks
+into the Share-With menu and uploads the file to Docspell.
+
+This is especially useful to quickly upload small things like shopping
+receipts.
+
+
+
+