diff --git a/docs/advanced.rst b/docs/advanced.rst index c31718e3..4b886a98 100644 --- a/docs/advanced.rst +++ b/docs/advanced.rst @@ -550,7 +550,7 @@ Stores the access data for cloud storage. This can be reused without modificatio config.json ------------------------ -Contains the server configuration. If you want to deploy Gokapi in multiple instances for redundancy (e.g. all instances share the same data), then the configuration file can be reused without modification. Otherwise you need to modify it before deploying (see below). Can be read-only, but might need write access when upgrading Gokapi to a newer version. Needs write access when re-running setup or changing the admin password. +Contains the server configuration. If you want to deploy Gokapi in multiple instances for redundancy (e.g. all instances share the same data), then the configuration file can be reused without modification. Otherwise you need to modify it before deploying (see below). Can be read-only, but might need write access when upgrading Gokapi to a newer version. Needs write access when re-running setup. Modifying config.json to deploy without setup @@ -565,8 +565,6 @@ If you want to deploy Gokapi to multiple instances that contain different data, +-----------+------------------------------------------------------------+----------------------+ | SaltFiles | Change to empty value | "SaltFiles": "", | +-----------+------------------------------------------------------------+----------------------+ -| Password | Change to empty value | "Password": "", | -+-----------+------------------------------------------------------------+----------------------+ | Username | Change to the username of your preference, | "Username": "admin", | | | | | | | if you are using internal username/password authentication | | @@ -575,7 +573,7 @@ If you want to deploy Gokapi to multiple instances that contain different data, Setting an admin password ==================================================== -If you are using internal username/password authentication, run the binary with the parameter ``--deployment-password [YOUR_PASSWORD]``. This sets the password and also generates a new salt for the password. This has to be done before Gokapi is run for the first time on the new instance. Alternatively you can do this on the orchestrating machine and then copy the configuration file to the new instance. +If you are using internal username/password authentication, run the binary with the parameter ``--deployment-password [YOUR_PASSWORD]``. This sets the password and also generates a new salt for the password. This has to be done before Gokapi is run for the first time on the new instance. Alternatively you can do this on the orchestrating machine and then copy the configuration file and database to the new instance. If you are using a Docker image, this has to be done by starting a container with the entrypoint ``/app/run.sh``, for example: ::