Xen Orchestra on Ubuntu 15.10 - Complete installation instructions
-
-
@DustinB3403 said:
@scottalanmiller That was a part of the guide I had seen when I was first setting this up....
double checking now
I'm testing without it and with Node 4.2.4.
-
@DustinB3403 said:
Install version 3.3.12
sudo npm -install -g [email protected]This line has a typo. The command is install not -install. Is there a reason that you are going for that specific version rather than just updating to current?
npm install -g npm -
@scottalanmiller the most recent version was unsupported.
So it had to be >=2.27 but less than version 5
-
@DustinB3403 said:
@scottalanmiller the most recent version was unsupported.
So it had to be >=2.27 but less than version 5
3.5.3 is current.
-
I don't see a user explanation in the instructions. Where does the user come from and what role does it play?
-
Don't mix
nodeandnpmversion.BTW, it should work with latest
nodeversion now. -
@scottalanmiller said:
I don't see a user explanation in the instructions. Where does the user come from and what role does it play?
Is this for me?
-
@johnhooks said:
@scottalanmiller said:
I don't see a user explanation in the instructions. Where does the user come from and what role does it play?
Is this for me?
It's for Dustin who wrote the instructions.
-
@scottalanmiller said:
@johnhooks said:
@scottalanmiller said:
I don't see a user explanation in the instructions. Where does the user come from and what role does it play?
Is this for me?
It's for Dustin who wrote the instructions.
Oh ok. I had a "user" in my playbook that needs replaced. I thought you were referring to that. I am using a variable for it now so you can just change the variable.
-
What is there to understand about it?
Following a base install of the server OS, i built a user named "xoadmin" which the mount directory uses /home/xoadmin/xo-web/dist/ in the .xo-sample.yaml file
-
Something is different or changed...
-
And now you discover why we release appliance with an updater and validated updates
Lodash team made a release 6 hours ago, and it broke everything. We are working on a way to avoid that, or reported this to them.
This stuff is sadly not very uncommon.
-
@olivier said:
And now you discover why we release appliance with an updater and validated updates
Lodash team made a release 6 hours ago, and it broke everything. We are working on a way to avoid that, or reported this to them.
This stuff is sadly not very uncommon.
How dare they break it!
-
@DustinB3403 said:
What is there to understand about it?
Following a base install of the server OS, i built a user named "xoadmin" which the mount directory uses /home/xoadmin/xo-web/dist/ in the .xo-sample.yaml file
Well the part ot understand is that you manually made a user and it wasn't made by the installer like most software does. If you are making a how to, you have to include the steps or else things are missing.
-
@olivier What's the best way to know what Node and NPM version should be used?
-
Ok, here's the updated playbook. Just add your hostname in /etc/ansible/hosts and your username in the variables file, it will do the rest.
-
@anonymous Experience ^^ (if the build fails).
In general, when there is a new big release of Node, dependencies can't catch the breaking changes for a time. That's why Node 5 broke the build for a time.
You can use the LTS version of Node to be safe: https://nodejs.org/en/blog/release/v4.2.0/
-
Hopefully LTS means more for Node than it does for ubuntu.
-
@scottalanmiller hahaha
