The global orchestration solution to manage and backup XCP-ng and XenServer.
Go to file
2018-01-02 22:29:02 +01:00
src fix(xosan): beta-is-over message (#2546) 2018-01-02 21:50:40 +01:00
tools chore: prettify non-source files 2017-12-06 13:52:12 +01:00
.editorconfig Minor fix in EditorConfig. 2015-06-11 08:54:58 +02:00
.eslintrc.js chore(package): update dependencies 2017-12-18 17:00:04 +01:00
.gitignore feat({backup,job}/overview): clearer state (#2023) 2017-03-23 09:42:23 +01:00
.npmignore Initial work on React/Redux. 2015-12-03 18:22:13 +01:00
.prettierrc.js chore(package): update dependencies 2017-12-18 17:00:04 +01:00
.travis.yml feat: yarn integration (#1813) 2016-12-07 14:36:51 +01:00
CHANGELOG.md changelog for 5.15 2017-12-29 16:04:44 +01:00
gulpfile.js chore(gulpfile): fix sourcemaps 2018-01-02 19:01:33 +01:00
ISSUE_TEMPLATE.md fix(issue template): use the word "current" instead of "actual" 2016-06-09 22:21:50 +02:00
LICENSE Explicit the license. 2015-04-10 12:06:46 +02:00
package.json chore(package): missing peer dependency 2018-01-02 22:29:02 +01:00
README.md feat(readme): add live chat link and icon 2017-01-16 14:54:57 +01:00
setup-tests.js fix: tests and coding style 2017-10-06 19:34:12 +02:00
yarn.lock chore(package): update Babel conf 2018-01-02 22:20:55 +01:00

Xen Orchestra Web Chat with us Build Status

XO-Web is part of Xen Orchestra, a web interface for XenServer or XAPI enabled hosts.

It is a web client for XO-Server.


Installation

XOA or manual install procedure is available here

Compilation

Production build:

$ npm run build

Development build:

$ npm run dev

Environment

NODE_ENV

Set to production it disables many checks which result in increased performance.

XOA_PLAN

  • 1: Free
  • 2: Starter
  • 3: Enterprise
  • 4: Premium
  • 5: Sources
if (process.env.XOA_PLAN < 5) {
  console.log('included only in XOA')
}

if (process.env.XOA_PLAN > 3) {
  console.log('included only in Premium and Sources')
}

How to report a bug?

If you are certain the bug is exclusively related to XO-Web, you may use the bugtracker of this repository.

Otherwise, please consider using the bugtracker of the general repository.

Process for new release

# Switch to the stable branch.
git checkout stable

# Fetches latest changes.
git pull --ff-only

# Merge changes of the next-release branch.
git merge next-release

# Increment the version (patch, minor or major).
npm version minor

# Go back to the next-release branch.
git checkout next-release

# Fetches the last changes (the merge and version bump) from stable to
# next-release.
git merge --ff-only stable

# Push the changes on git.
git push --follow-tags origin stable next-release

# Publish this release to npm.
npm publish

License

AGPL3 © Vates SAS