Welcome. Juju-GUI is a web-based GUI for Juju. Juju lets you deploy connected services to the cloud in a convenient, vendor-neutral, and powerful way. The GUI lets you visualize and manage your work more intuitively from a web browser.
Juju-GUI code is hosted on Github
Juju-GUI bugs are tracked on on Launchpad.
See also:
- a stable demo,
- a demo of trunk,
- the juju quickstart plugin,
- our blog, and
- the user-facing docs.
Deploying the GUI is easiest with the juju quickstart plugin or the Juju GUI charm. If you want to simply use the GUI, please try those.
If you want to develop the GUI, or you have a deployment goal that the charm does not and cannot support, you can try the Makefile commands. The most useful available commands are shown by the make help command.
You will typically want to run one of make prod, make debug or make devel to deploy an environment. You might also run make test-debug and make test-prod to check that everything is ok, and make docs to generate the available documentation for both project and code. See the HACKING file for details.
Some configurable parameters may be found in three files:
config.jsapp/config-debug.jsapp/config-prod.js
If you are using the charm, the end-user configuration is available from the charm configuration.
When giving a demonstration with the Gui you often want to help the visual presentation by showing icons for charms that are not yet reviewed and recommended. Since you have reviewed the charms you intend to use in your presentation, you may override the safety features by manually setting "demo-mode" into your localStorage for the Gui website. You can do this using the developer tools for the browser you're demonstrating with.
Open a console and enter:
localStorage.setItem('demo-mode', true);By default, the Juju GUI only allows containers' management on providers fully supporting containerization, including creation/deletion and networking (e.g. port forwarding for exposed services).
If containerization is not supported in the current Juju environment, the header of the third column in machine view shows the "Sub-containers not supported" message.
When giving a demonstration, or in the case the networking aspects are manually handled, it is possible to override those checks and force containers support to be enabled by activating the containers flag, like in the example below:
https://<juju-gui-address>/:flags:/containers