The web interface for Composer!
Composer generates custom images suitable for deploying systems or uploading to the cloud. It integrates into Cockpit as a frontend for Lorax Composer.
Here's where to get the code:
$ git clone https://github.com/weldr/cockpit-composer.git
$ cd cockpit-composer/
The remainder of the commands assume you're in the top level of the Cockpit Composer git repository checkout.
On Fedora or Red Hat Enterprise Linux:
- First install Cockpit on your local machine as described in: https://cockpit-project.org/running.html.
- Next install and start lorax-composer:
$ sudo yum install lorax-composer
$ sudo systemctl start lorax-composer
- Cockpit Composer uses Node.js during development. Node.js is not used at runtime. To make changes on Cockpit you'll want to install Node.js, NPM.
$ sudo yum install nodejs npm
In addition, for testing, the following dependencies are required:
$ sudo yum install curl expect \
libvirt libvirt-client libvirt-daemon libvirt-python \
python python-libguestfs python-lxml libguestfs-xfs \
python3 libvirt-python3 \
libguestfs-tools qemu qemu-kvm rpm-build jq
Run
$ make
to build everything. You can only run make from the top-level and it will always rebuild the Cockpit Composer.
Cockpit Composer is built using React. For inspecting the React component hierarchy, including component props and state, you can run
$ npm run build:debug
End-to-End Test Running Guide.
Cockpit Composer uses ESLint to automatically check
JavaScript code style in .js files.
The linter is executed within every build as a webpack preloader.
For developer convenience, the ESLint can be started explicitly by:
$ npm run eslint
Rules configuration can be found in the package.json file.
It's easy to set up your local Linux machine for rapid development of Cockpit Composer's JavaScript code. Run this command from your top level Cockpit Composer checkout directory, and make sure to run it as the same user that you'll use to log into Cockpit Composer below.
$ mkdir -p ~/.local/share/cockpit
$ ln -s $(pwd)/public ~/.local/share/cockpit/welder
This will cause cockpit to read JavaScript and HTML files directly from the built package output directory instead of using the installed Cockpit UI files.
Now you can log into Cockpit Composer on your local Linux machine at the following address. Use the same user and password that you used to log into your Linux desktop.
After every change to your sources, run make to update all the webpacks, and reload cockpit in your browser.
.
├── /components/ # Shared or generic UI components
│ ├── /Layout/ # Website layout component
│ ├── /Link/ # Link component to be used insted of <a>
│ └── /... # etc.
├── /core/ # Core framework
│ ├── /actions/ # Redux actions
│ ├── /reducers/ # Redux reducers
│ ├── /sagas/ # Redux saga files
│ ├── /apiCalls.js # All API calls to lorax-composer
│ ├── /constants.js # lorax-composer API path
│ ├── /history.js # Handles client-side navigation
│ ├── /router.js # Handles routing and data fetching
│ ├── /selectors.js # Simple “selector” for Redux
│ ├── /store.js # Application state manager (Redux)
│ └── /utils.js # Utility for group API URL
├── /data/ # Provide API for internal use
│ ├── /BlueprintApi.js # Blueprint API
│ ├── /MetadataApi.js # Metadata API
│ └── /NotificationsApi.js # Notification API
├── /node_modules/ # 3rd-party libraries and utilities
├── /pages/ # React components for web pages
│ ├── /blueprint/ # Blueprint page
│ ├── /blueprints/ # Blueprints page
│ ├── /blueprintEdit/ # Edit blueprint page
│ └── /error/ # Error page
├── /po/ # Translated result by Zanata
├── /public/ # Static files
│ ├── /dist/ # The folder for compiled output
│ ├── /js/ # Javascript files included in index.ejs
│ ├── /custom.css # CSS file included in index.ejs
│ ├── /manifest.json # manifest file for Cockpit integration
│ └── /index.ejs # Template for index.html
├── /test/ # End to end test
├── /utils/ # Utility and helper classes
│── .tasks # Tasks triggered by Cockpit bot
│── .travis.yml # Travis CI settings
│── babel.config.js # babel configurations
│── cockpit-composer.spec.in # Cockpit-composer spec file
│── Dockerfile.buildrpm # Dockerfile for building RPM on Travis
│── io.weldr.cockpit-composer.metainfo.xml # Makes Composer appear on Cockpit's "Applications" page
│── main.js # React application entry point
│── Makefile # Makefile
│── package.json # The list of project dependencies and NPM scripts
│── routes.json # This list of application routes
│── rpmversion.sh # Generate the version and release strings for spec file
|── webpack.config.js # Bundling and optimization settings for Webpack
└── zanata.xml # zanata settingsTo keep Cockpit Composer working with Cockpit API all code should follow the following rules.
- All urls in the html and javascript need to use relative paths.
- All requests to the API should be made using
utils.apiFetch. Any non APIfetchrequests must usecredentials: 'same-origin'so that cookies are included with those ajax requests. - Use hashes for navigation within the SPA so that cockpit can keep the top level location display up to date.
This project can be packaged as either a noarch rpm or an srpm.
$ make rpm # Or, `make srpm`For a general guide on how to write translatable strings, see weldr.io
All npm run targets that start with translate: need zanata-js to be installed. Install it with the usual
npm install zanata-js.
There are a lot of parts involved in translating a string. Here's an overview of the process, from start to finish:
Step 1. During development, the developer adds a translatable string. See weldr.io
for details on how to indicate that the string is translatable, and what the string may contain. In general, the string
is added using react-intl MessageDescriptors, but without explicit id attributes.
Step 2. The developer runs npm run translations:push. As part of this process, babel-plugin-react-intl-auto
will add id attributes to all of the messages, and babel-plugin-react-intl
will extract all of the messages to JSON files, written to ./build/messages. react-intl-po is
used to collect the JSON files into a gettext-style POT file, and the POT file is uploaded to Zanata.
Step 3. Translators provide translations on Zanata.
Step 4. The developer runs npm run translations:pull and npm run translations:po2json. This downloads the translations from
Zanata as gettext-style .po files and converts the .po files back to JSON.
Step 5. The user runs cockpit-composer. Based on the user's browser configuration, cockpit-composer determines the user's preferred
language, and if translations are available, these translations are provided to react-intl's <IntlProvider>. react-intl
then displays translated strings where possible.
When the project is ready for a new release, do the following:
- Tag the release with
make NEWTAG=X.Y.Z tag, bumping .Z to the next version unless there are major changes. - Edit the commit list to reflect the changes that will be visible to users (it shows up on the GitHub Releases page)
- Sign the tag with your GPG key
(an editor should open automatically, and gpg is required to be setup in order to sign the tag).
Then push the tag with git push --tags. This will trigger
cockpituous
to build a new release of cockpit-composer.
Finally, import the new .srpm into the appropriate RHEL release.
This source code is licensed under the MIT license found in the LICENSE.txt file.
Made with ♥ by the Welder team, Cockpit team, and contributors