Replaces installing a patched anaconda-webui RPM from the forge's package registry: installer/anaconda-webui/vendor/ is upstream release 86 verbatim (see its PROVENANCE.md), and installer/Containerfile builds it with upstream's own `make install` in a native-platform stage, then copies the result over stock Fedora anaconda-webui. The produced file set matches Fedora's anaconda-webui-86-1.fc46 exactly. Edits to the installer UI now happen in vendor/ and ship on the next `task build-installer-iso`, with no RPM, registry or CI in between. Also follows bootc-image-builder's rename of --bootc-installer-payload-ref to --installer-payload-ref. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
46 lines
1.5 KiB
ReStructuredText
46 lines
1.5 KiB
ReStructuredText
Anaconda Web UI
|
|
===============
|
|
|
|
Getting the source
|
|
------------------
|
|
|
|
Here's where to get the code::
|
|
|
|
git clone https://github.com/rhinstaller/anaconda-webui.git
|
|
cd anaconda-webui
|
|
|
|
Development instructions
|
|
------------------------
|
|
|
|
See `<HACKING.rst>`_ and `<test/README.rst>`_ for details about how to efficiently change the code,
|
|
run, and test it.
|
|
|
|
Automated release
|
|
-----------------
|
|
|
|
The intention is that the only manual step for releasing a project is to create
|
|
a signed tag for the version number, which includes a summary of the noteworthy
|
|
changes::
|
|
|
|
123
|
|
|
|
- this new feature
|
|
- fix bug #123
|
|
|
|
Pushing the release tag triggers the `release.yml <.github/workflows/release.yml>`_
|
|
`GitHub action <https://github.com/features/actions>`_ workflow. This creates the
|
|
official release tarball and publishes as upstream release to GitHub.
|
|
|
|
The Fedora and COPR releases are done with `Packit <https://packit.dev/>`_.
|
|
see the `packit.yaml <./packit.yaml>`_ control file.
|
|
|
|
Automated maintenance
|
|
---------------------
|
|
|
|
It is important to keep your `NPM modules <./package.json>`_ up to date, to keep
|
|
up with security updates and bug fixes. This is done with dependabot, see the
|
|
`dependabot.yml <./.github/dependabot.yml>`_ control file.
|
|
Similarly, translations are refreshed every Tuesday evening (or manually) through the
|
|
`weblate-sync-po.yml <.github/workflows/weblate-sync-po.yml>`_ action.
|
|
Conversely, the PO template is uploaded to weblate every day through the
|
|
`weblate-sync-pot.yml <.github/workflows/weblate-sync-pot.yml>`_ action.
|