diff --git a/docs/source/_static/images/admin_panel_bsp_only.png b/docs/source/_static/images/admin_panel_bsp_only.png old mode 100644 new mode 100755 index 3255b3e..c407ca8 Binary files a/docs/source/_static/images/admin_panel_bsp_only.png and b/docs/source/_static/images/admin_panel_bsp_only.png differ diff --git a/docs/source/getting_started.rst b/docs/source/getting_started.rst index 9c98c5b..50c726b 100644 --- a/docs/source/getting_started.rst +++ b/docs/source/getting_started.rst @@ -96,6 +96,7 @@ content of the configuration file, you will see that it is only a reference to t .. note:: If you create an own configuration file, you can also store it in the "/etc/everest" directory and create a symbolic link to it like "ln -sf /etc/everest/my-config.yaml /etc/everest/config.yaml". + The file where the "config.yaml" symbolic link points to is preserved during the update process. .. code-block:: bash diff --git a/docs/source/troubleshooting.rst b/docs/source/troubleshooting.rst index 4f06fbb..9d59c93 100644 --- a/docs/source/troubleshooting.rst +++ b/docs/source/troubleshooting.rst @@ -69,7 +69,7 @@ The most important points are summarised here: `libocpp documentation `_. -I tried to compile chargebyte's Hardware EVerest Modules, but it fails to build. How can it fix this? +I tried to compile chargebyte's Hardware EVerest Modules, but it fails to build. How can I fix this? ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ The EVerest mainline development is very dynamic and doesn't guarantee any diff --git a/includes b/includes index 7530394..c6a94a1 160000 --- a/includes +++ b/includes @@ -1 +1 @@ -Subproject commit 7530394d396e81a80ceabbf94119dbfec42f02cf +Subproject commit c6a94a17d6cfddc76617dc5e8a7d4907b7844b16