From 86da5b335ebd5a48ef27cc73af60d69cd953c348 Mon Sep 17 00:00:00 2001 From: codedge Date: Tue, 18 Aug 2020 18:15:16 +0200 Subject: [PATCH] Updated Debugging (markdown) --- Debugging.md => Debugging-&-FAW.md | 15 +++++++++++++-- 1 file changed, 13 insertions(+), 2 deletions(-) rename Debugging.md => Debugging-&-FAW.md (67%) diff --git a/Debugging.md b/Debugging-&-FAW.md similarity index 67% rename from Debugging.md rename to Debugging-&-FAW.md index a106061..137dde0 100644 --- a/Debugging.md +++ b/Debugging-&-FAW.md @@ -1,6 +1,17 @@ +## FAQ + +### Missing or wrong application key + +**Error**: `https://github.com/invoiceninja/dockerfiles/wiki/prerequisites#generate-an-application-key` + +**Solution** +You did not properly insert a valid application key. Please [check here](https://github.com/invoiceninja/dockerfiles/wiki/prerequisites#generate-an-application-key) and the linked blog post. + + +## Debugging Even when running your Invoice Ninja setup with Docker - errors can occur. Depending on where the error happens - the webserver, Invoice Ninja or the database - different log files can be responsible. -## Show logs without `docker-compose` +### Show logs without `docker-compose` If you are not running `docker-compose` you first need to find the container id for your php container with `docker ps`. Then you can run @@ -10,7 +21,7 @@ docker logs -f This gives you a constant output of the log files for the php container. -## Show logs with `docker-compose` +### Show logs with `docker-compose` If you are running the `docker-compose` setup you can output all logs, from all containers, with the following command