3 Commits

Author SHA1 Message Date
Dan Pollak
a3770eb721 Node 18 is no longer a requirement
Signed-off-by: Dan Pollak <danpollak2@gmail.com>
2024-06-03 17:45:34 -05:00
Dustin B
5a04a2aed6 Update README.md
Removal of the prepackaged installation, with XOlite around the corner a minimized installation won't be required when released.
2024-02-09 15:45:44 -05:00
Dustin B
bfc606a207 Merge pull request #122 from Jarli01/dp_sudo
Remove remaining `sudo` instances
2024-01-05 11:47:17 -05:00
2 changed files with 1 additions and 3 deletions

View File

@@ -41,8 +41,6 @@ To maintain your installation from Source or from this repo. (either prepackaged
This script automates the manual process which can be [found here](https://xen-orchestra.com/docs/from_the_sources.html) as well as removes a few feature restrictions that otherwise would need to be changed manually if following the manual installation process. This script is not officially supported by the Vates team, but is supported by this community. This script automates the manual process which can be [found here](https://xen-orchestra.com/docs/from_the_sources.html) as well as removes a few feature restrictions that otherwise would need to be changed manually if following the manual installation process. This script is not officially supported by the Vates team, but is supported by this community.
## Prepackaged Installation temporarily disabled while I sort out the credentials issue.
# Self-signed SSL # Self-signed SSL
If you are running this internally and need SSL (recommended) follow the below steps to create a self-signed SSL key and certificate; while browsers will still say the connection is unsecured, this is because the certificate isn't from a public authority and is on your LAN. You can add this cert to your systems root authority if it want to to remove the warning. Alternatively a reverse proxy can be used for public facing installations. If you are running this internally and need SSL (recommended) follow the below steps to create a self-signed SSL key and certificate; while browsers will still say the connection is unsecured, this is because the certificate isn't from a public authority and is on your LAN. You can add this cert to your systems root authority if it want to to remove the warning. Alternatively a reverse proxy can be used for public facing installations.

View File

@@ -37,7 +37,7 @@ echo "$yarn_repo" | tee /etc/apt/sources.list.d/yarn.list
/bin/chmod +x $n_location /bin/chmod +x $n_location
# Install node via n # Install node via n
n 18 n lts
# Symlink node directories # Symlink node directories
ln -s /usr/bin/node /usr/local/bin/node ln -s /usr/bin/node /usr/local/bin/node