summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorAndrew Godwin2022-11-27 00:39:28 -0700
committerAndrew Godwin2022-11-27 00:39:28 -0700
commit9cd1fccde5454435299069c32ef57513ae886995 (patch)
treeae20e7a60d885bf590ba58a126643cf66c77d42e
parent43771601550577beca38db88643128972ece1925 (diff)
downloadtakahe-9cd1fccde5454435299069c32ef57513ae886995.tar.gz
takahe-9cd1fccde5454435299069c32ef57513ae886995.tar.bz2
takahe-9cd1fccde5454435299069c32ef57513ae886995.zip
Tamper down the worker warning
-rw-r--r--docs/installation.rst8
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/installation.rst b/docs/installation.rst
index fc93d1f..cd9799f 100644
--- a/docs/installation.rst
+++ b/docs/installation.rst
@@ -22,12 +22,12 @@ Prerequisites
* Writable local directory (must be accessible by all running copies!)
Note that ActivityPub is a chatty protocol that has a lot of background
-activity, so you will need a platform that can run *background tasks*, in
+activity, so you will need to run *background tasks*, in
order to fetch profiles, retry delivery of posts, and more.
-This means that a "serverless" platform like AWS Lambda or Google Cloud Run is
-not enough by itself; while you can use these to serve the web pages if you
-like, you will need to run the Stator runner somewhere else as well.
+Ideally, you would choose a platform where you can run our worker process in
+the background continuously, but for small installations we have a URL you can
+call periodically instead - see "What To Run", below.
The flagship Takahē instance, `takahe.social <https://takahe.social>`_, runs
inside of Kubernetes, with one Deployment for the webserver and one for the