Xen Orchestra - Community Edition - Installing with Yarn
-
Now would be a good time to decide between your and SAM's GH repository. The link you posted goes to yours, but the instructions use his.
-
@Danp said in Xen Orchestra - Community Edition - Installing with Yarn:
Now would be a good time to decide between your and SAM's GH repository. The link you posted goes to yours, but the instructions use his.
Bad habits... dang it.
Corrected.
-
@DustinB3403 said in Xen Orchestra - Community Edition - Installing with Yarn:
@Danp yeah I figured as much, the switch branch works and is my default
Just because you like to make things harder than necessary doesn't justify you passing that on to everyone else.
-
@DustinB3403 said in Xen Orchestra - Community Edition - Installing with Yarn:
sudo bash
sudo curl https://raw.githubusercontent.com/Jarli01/xenorchestra_updater/master/xo-update.sh | bash -s -- -fSo just to confirm for anyone who might be a bit new to all this stuff (asking for a friend) ...
Once you have XO installed, you run the above command to update your existing installation, right?
I had just been updating it, but you said to rebuild/reinstall which is what I have been doing.
-
@BRRABill said in Xen Orchestra - Community Edition - Installing with Yarn:
@DustinB3403 said in Xen Orchestra - Community Edition - Installing with Yarn:
sudo bash
sudo curl https://raw.githubusercontent.com/Jarli01/xenorchestra_updater/master/xo-update.sh | bash -s -- -fSo just to confirm for anyone who might be a bit new to all this stuff (asking for a friend) ...
Once you have XO installed, you run the above command to update your existing installation, right?
I had just been updating it, but you said to rebuild/reinstall which is what I have been doing.
By using the force option (or switch build if you want to go to next-release or back to stable) the scripts enable the ability to import your configuration from any other XO installations you may have.
-
@BRRABill If you are running the installation for the first time on a system, it will be current, but without the enabled functionality.
-
@DustinB3403 said in Xen Orchestra - Community Edition - Installing with Yarn:
@BRRABill said in Xen Orchestra - Community Edition - Installing with Yarn:
@DustinB3403 said in Xen Orchestra - Community Edition - Installing with Yarn:
sudo bash
sudo curl https://raw.githubusercontent.com/Jarli01/xenorchestra_updater/master/xo-update.sh | bash -s -- -fSo just to confirm for anyone who might be a bit new to all this stuff (asking for a friend) ...
Once you have XO installed, you run the above command to update your existing installation, right?
I had just been updating it, but you said to rebuild/reinstall which is what I have been doing.
By using the force option (or switch build if you want to go to next-release or back to stable) the scripts enable the ability to import your configuration from any other XO installations you may have.
But I mean you recommend this over the straight "updating" the @olivier describes on the XO site.
-
@BRRABill I think you are missing the two things being discussed.
Recently @olivier and his team enabled the use of Yarn (you can find instructions here on how to install this and then upgrade) as you have in the past.
Or you can export your settings, and create a new installation, with Yarn packed in. From there just import your configuration settings.
-
Ah, OK.
Sorry was out for a few days, just getting my brain warmed back up!
-
@BRRABill No problem.
The Yarn package does a better job of managing NPM, so we had to update the installation process, along with determine a way that we could install Yarn into existing systems.
Building a new system is almost easier in that you can export and import your configurations.
So there is no "good" reason to be stuck on one.
-
@DustinB3403 - I just signed up to say a massive thank you for this - I've been struggling with the previous instructions and going round in circles with no success. I've now used your script to build successfully on a ubuntu 16.04 server and am up and running.
I did find a couple of issues along the way - firstly, is there a typo in the command line? I think the correct path should be github.com/Jarli01/xenorchestra_installer/master/xo_install.sh - I only got it working in the first place by downloading the script and running locally.
Secondly, on my system at least, yarn wasn't installed, so the first run of the script failed - it was an easy enough correction to make, but could be checked and covered within the script?
Anyway, thanks again
Noel Weston
-
@noelweston welcome to MangoLassi!
-
@noelweston I believe the path should actually be -- https://raw.githubusercontent.com/Jarli01/xenorchestra_installer/master/xo_install.sh
-
@Danp - OK - as I said, I've got round it - but I think there's a spare "edit" in the first post / instructions?
@scottalanmiller - thanks!
-
@noelweston said in Xen Orchestra - Community Edition - Installing with Yarn:
Secondly, on my system at least, yarn wasn't installed
Looks like the actual command to install is missing. According to their website, the proper command would be
sudo apt-get update && sudo apt-get install yarn. -
@Danp - Yes, that's what I ended up doing. Might just be worth either adding to the script (if that doesn't cause other issues) or at least warning for noobs like me?
-
I'm sure @DustinB3403 will get it fixed up shortly.
-
I've updated the script (sorry, not sure how I forgot the yarn install portion...) and tested both the installation, and then the force to enable the added functionality.
All is working as intended.
Also @noelweston welcome to the community, and I'm glad that I made your life a bit easier.
-
Hi @DustinB3403
I am trying to update the xo community install however after running the script successfully the xo web and server version remains old. I can see the master stable source is updated with latest version.
https://github.com/vatesfr/xo-web - 5.10.4
https://github.com/vatesfr/xo-server - 5.10.0After running the updater script my xo is still at xo-server 5.8.0 and xo-web 5.9.0.
-
@shwetkprabhat Can you show us the console output from running the update script?
Also, show us the exact command you issued to perform the upgrade.
