From d3244e7bff01791f7ee22ac964a470a8fe5fb009 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Roni=20V=C3=A4yrynen?= Date: Sat, 25 Jun 2022 14:20:34 +0300 Subject: [PATCH] Updated Home (markdown) --- Home.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/Home.md b/Home.md index 7d9aed2..e5b549f 100644 --- a/Home.md +++ b/Home.md @@ -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.