pcs-web-ui's Introduction

PCS WEB UI

Web interface for pcs - a Corosync and Pacemaker configuration tool.

Prerequisites

Git
Node.js (with NPM)

Preparation

git clone <repository-url> this repository
change into the new directory
make init

Development

Running dev environment

make app
make dev
- dev backend doesn't run fully featured backend mock
- it runs only scenario with limited features
Open http://localhost:3000 to view it in the browser

Running tests

make tests

Building and installation

make build
- you can use BUILD_USE_CURRENT_NODE_MODULES=true make build if correct node modules already exists
production build is created inside build directory
content of build directory copy to pcsd/public/ui/ directory

Building and installation for cockpit

BUILD_FOR_COCKPIT=true make build
production build is created inside build directory
content of build directory copy (or symlink) to the path where cockpit will find it, e.g.
- mkdir -p ~/.local/share/cockpit
- ln -snf "$PWD"/build ~/.local/share/cockpit/ha-cluster

pcs-web-ui's People

Contributors

Stargazers

Watchers

pcs-web-ui's Issues

How to build cockpit plugin locally?

I found this project requires to Nexus repo for packaging.

`make build` requires an interactive response

Running make build may occasionally end up with a request for interactive response like this:

 Need to install the following packages:
   npm
 Ok to proceed? (y)

It comes from npx npm ci.
The problem is, that whenever make build is run from a script (or an Ansible playbook), the script gets stuck as npx is waiting for a response forever. Is there perhaps a npx parameter that would make it assume yes?

Recommend Projects