From c6e9f5dc0329cd9b2f23d3f5783231ac30082fcf Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?J=C3=A9r=C3=A9my=20Bobbio=20=28Lunar=29?=
 <lunar@softwareheritage.org>
Date: Mon, 20 Feb 2023 15:21:49 +0100
Subject: [PATCH] Document usage of pifpaf for manual builds

The README mentions that building everything via tox uses pifpaf
to run the required postgresql database. It feels like a good idea
to also add pifpaf to the command lines required for the manual builds.
---
 README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index c8025add..f9801a6f 100644
--- a/README.md
+++ b/README.md
@@ -61,7 +61,7 @@ mainly in 3 steps:
 ### 1. Generate documentation assets for all modules
 
     $ cd swh-environment
-    $ make docs-assets
+    $ pifpaf run postgresql -- make docs-assets
 
 This will *not* build the documentation in each module (there is `make docs`
 for that).
@@ -70,7 +70,7 @@ for that).
 ### 2. Build the api docs for all swh python packages
 
     $ cd swh-docs/docs
-    $ make apidoc
+    $ pifpaf run postgresql -- make apidoc
 
 ### 3. Build the documentation
 
-- 
GitLab