HACKING: Document how to use locally built cockpit-ws
This is useful for validating PRs like #13376 Closes #13389
This commit is contained in:
parent
f8e80d09a3
commit
624dc8a0eb
15
HACKING.md
15
HACKING.md
|
@ -165,7 +165,7 @@ git checkout directory, run the following, and log into Cockpit again:
|
|||
|
||||
$ rm ~/.local/share/cockpit
|
||||
|
||||
## Working on your local machine: Web server resources
|
||||
## Working on your local machine: Web server
|
||||
|
||||
To test changes to the login page or any other resources, you can bind-mount
|
||||
the build tree's `dist/static/` directory over the system one:
|
||||
|
@ -184,6 +184,19 @@ To make Cockpit again use the system-installed code, simply umount these again:
|
|||
$ sudo umount /usr/share/cockpit/static/ /usr/share/cockpit/branding/
|
||||
$ systemctl stop cockpit.service
|
||||
|
||||
Similarly, if you change cockpit-ws itself, you can make the system (systemd
|
||||
units, cockpit-tls, etc.) use that:
|
||||
|
||||
$ sudo mount -o bind cockpit-ws /usr/libexec/cockpit-ws
|
||||
|
||||
On Debian based OSes, the path will be `/usr/lib/cockpit/cockpit-ws` instead.
|
||||
You need to disable SELinux with
|
||||
|
||||
$ sudo setenforce 0
|
||||
|
||||
for this to work, as your local build tree does not otherwise have the expected
|
||||
SELinux type.
|
||||
|
||||
## Working on Cockpit using Vagrant
|
||||
|
||||
It is also possible to use a Vagrant virtual machine to develop Cockpit.
|
||||
|
|
Loading…
Reference in New Issue