History

Julien Fontanet 5d82f2696e fix(xo-web/new-vm): handle both template_info.disks and VDIs Related to 3be45c7f4		2024-02-23 16:35:32 +01:00
..
src	fix(xo-web/new-vm): handle both template_info.disks and VDIs	2024-02-23 16:35:32 +01:00
tools	chore: format with Prettier	2023-11-20 12:34:30 +01:00
.babelrc.js	chore: enforce strict mode for CJS files	2022-02-22 12:34:41 +01:00
.eslintrc.js	chore(eslint): only use @babel/eslint-parser for pkgs using Babel	2021-04-23 14:47:34 +02:00
.npmignore	feat: unified .npmignore for all packages	2021-04-07 13:58:14 +02:00
gulpfile.js	chore: update dev deps	2023-05-22 10:01:54 +02:00
LICENSE	feat(xo-web): move all files to packages/xo-web	2018-02-07 10:18:09 +01:00
package.json	feat: technical release (#7365 )	2024-02-09 10:09:09 +01:00
README.md	fix(*/README): legacy project URLs	2020-05-27 10:04:00 +02:00
setup-tests.js	chore: enforce strict mode for CJS files	2022-02-22 12:34:41 +01:00

README.md

Xen Orchestra Web

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?

Please consider using the bugtracker.

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