@aqua-calc All too easy! Works flawlessly on Ubuntu.
Easier to setup an Ubuntu VM then to deal with CentSO 7 for the time being.
Thx,
TK
@aqua-calc All too easy! Works flawlessly on Ubuntu.
Easier to setup an Ubuntu VM then to deal with CentSO 7 for the time being.
Thx,
TK
@aqua-calc Thx!
Started a Ubuntu 18.04 installation just a few moments ago. I'll give these a shot.
Guessing there's nothing for Cent OS , Fedora or RHEL yet then?
Thx,
TK
Hey All,
Has anyone the correct instructions for building Xen Orchestra?
Pulled the master copy from here: https://github.com/vatesfr/xen-orchestra
But getting errors like these, amongst many of them:
npm install && npm run build
* vhd-cli:build â Error: 127
* xo-server-sdn-controller:build â Error: 127
src/index.js -> dist/index.js
src/density-plan.js -> dist/density-plan.js
SyntaxError: src/index.js: Unexpected token (135:32)
133 | }
134 |
> 135 | _addPlan(mode, { name, pools, ...options }) {
| ^
136 | pools = uniq(pools)
137 |
138 | // Check already used pools.
* xo-server-load-balancer:build â Error: 1
[17:37:59] Using gulpfile ~/xen-orchestra/packages/xo-web/gulpfile.js
[17:37:59] Starting 'build'...
[17:37:59] Starting 'buildPages'...
[17:37:59] Starting 'buildScripts'...
[17:37:59] Starting 'buildStyles'...
[17:37:59] Starting 'copyAssets'...
[17:38:01] 'buildStyles' errored after 1.49 s
[17:38:01] Error: Missing binding /root/xen-orchestra/node_modules/node-sass/vendor/linux-x64-57/binding.node
Node Sass could not find a binding for your current environment: Linux 64-bit with Node.js 8.x
Found bindings for the following environments:
- Linux 64-bit with Node.js 10.x
This usually happens because your environment has changed since running `npm install`.
Run `npm rebuild node-sass` to download the binding for your current environment.
at module.exports (/root/xen-orchestra/node_modules/node-sass/lib/binding.js:15:13)
at Object.<anonymous> (/root/xen-orchestra/node_modules/node-sass/lib/index.js:14:35)
at Module._compile (module.js:653:30)
at Object.Module._extensions..js (module.js:664:10)
at Module.load (module.js:566:32)
at tryModuleLoad (module.js:506:12)
at Function.Module._load (module.js:498:3)
at Module.require (module.js:597:17)
at require (internal/module.js:11:18)
at Object.<anonymous> (/root/xen-orchestra/node_modules/gulp-sass/index.js:162:21)
[17:38:01] 'build' errored after 1.5 s
[17:38:01] The following tasks did not complete: buildPages, buildScripts, copyAssets
[17:38:01] Did you forget to signal async completion?
* xo-web:build â Error: 1
â 59
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! @ build: `scripts/run-script --parallel build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the @ build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2019-10-19T21_38_01_331Z-debug.log
[root@xoa-org01 xen-orchestra]#
[root@xoa-org01 n]#
[root@xoa-org01 n]#
[root@xoa-org01 n]# n
installed : v8.16.2 (with npm 6.4.1)
[root@xoa-org01 n]# node -v
v8.16.2
[root@xoa-org01 n]# cd /root/
Looks like the install has changed since these instructions were published:
Trying on CentOS 7. Hoping there's newer instructions for CentOS. Will try on Debian if CentOS 7 fails.
Is there newer instructions about the environment setup on CentOS 7 and subsequent compilation of the Xen Orchestra?
Thx,
TK