Updated Home (markdown)

Roni Väyrynen
2022-06-25 14:20:34 +03:00
parent fe638e0ba3
commit d3244e7bff

@@ -25,7 +25,7 @@ PATH_TO_HTTPS_CERT=$INSTALLDIR/xo.crt
PATH_TO_HTTPS_KEY=$INSTALLDIR/xo.key
AUTOCERT="true"
```
Now whenever install/update is ran with `xo-install.sh`, after xo-server service is started a new certificate/key pair is created to `/opt/xo/xo.crt`/`/opt/xo/xo.key` and Xen Orchestra will use them. `AUTOCERT` option will ensure that these files are autogenerated if they do not exist.
Now whenever install/update is ran with `xo-install.sh`, after xo-server service is started a new certificate/key pair is created to `/opt/xo/xo.crt`/`/opt/xo/xo.key` and Xen Orchestra will use them. `AUTOCERT` option will ensure that these files are autogenerated if they do not exist.
* Self-signed certificate, manually created
@@ -59,6 +59,8 @@ PATH_TO_HTTPS_KEY="/path/to/your/keyfile"
Run install/update with `xo-install.sh`
Note that if using non-root user in `xo-install.cfg`, this user needs to have appropriate read (or read/write if AUTOCERT is set to true) permissions to directory where defined certificate/key are located.
#### Non-root user
Script fully supports using a non-root user to run Xen Orchestra and will take care of everything for you. Couple things to note: script still needs to be run as root and any SELinux related permissions aren't modified.