congrats on the xen 4.19 release (manager ;)! love these videos, (and really appreciate the timestamps!) as I watch them while compiling the new version :) one recommendation I have would be to link to the blog post(s) you mention in the description. adding the backups status to the XO6 dashboard is very cool! tbh, i forget there is a dashboard in 5.x so looking forward to giving it a try in 6.x! i think having the tree view and the dashboard by default (instead of home) will make the new home screen much better than 5.x.
Would be nice if you could add the xo-cli default to the xcp-ng servers instead of relying on npm and internet to install it. It was rather hard to install it on our test environment because of the need of a http proxy. I had to add it not only to the environment, but also to curl, npm and git (on the latter two I had to use the --global flag to add the http proxy).
Hi! XO CLI is bundled in XOA, there's no point of having it in the Dom0 since it's only meant to be for control XO API, not XCP-ng API (otherwise, you can use xe). Using Node in the Dom0 is also a very bad idea and will augment the attack surface. The right approach is to leave the Dom0 untouched as possible and only interact via XO API or XCP-ng API. Also, the new XO API using REST means a simple HTTP GET/PUT call can send orders, reducing the need for another client.
![Noob To Max With DRAGON REWORK In Blox Fruits [FULL MOVIE]](http://i.ytimg.com/vi/LnBMOinoOvA/mqdefault.jpg)
congrats on the xen 4.19 release (manager ;)!
love these videos, (and really appreciate the timestamps!) as I watch them while compiling the new version :)
one recommendation I have would be to link to the blog post(s) you mention in the description.
adding the backups status to the XO6 dashboard is very cool! tbh, i forget there is a dashboard in 5.x so looking forward to giving it a try in 6.x! i think having the tree view and the dashboard by default (instead of home) will make the new home screen much better than 5.x.
Marc is the guy to congrats for the timestamp, a big thanks to him!
Thanks for the feedback, we'll add the links :)
Would be nice if you could add the xo-cli default to the xcp-ng servers instead of relying on npm and internet to install it. It was rather hard to install it on our test environment because of the need of a http proxy. I had to add it not only to the environment, but also to curl, npm and git (on the latter two I had to use the --global flag to add the http proxy).
Hi! XO CLI is bundled in XOA, there's no point of having it in the Dom0 since it's only meant to be for control XO API, not XCP-ng API (otherwise, you can use xe). Using Node in the Dom0 is also a very bad idea and will augment the attack surface. The right approach is to leave the Dom0 untouched as possible and only interact via XO API or XCP-ng API. Also, the new XO API using REST means a simple HTTP GET/PUT call can send orders, reducing the need for another client.