-
Notifications
You must be signed in to change notification settings - Fork 3.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make ui_next the default UI #15347
Make ui_next the default UI #15347
Conversation
Just a general comment - having links with 'here' as the text don't work well with screen-readers. It is better to have something more descriptive in that bit of text. |
5628c2c
to
8b128d4
Compare
4d03992
to
ed5e9c7
Compare
bebb513
to
716e5be
Compare
In the container I get:
|
@@ -79,8 +77,8 @@ function Dashboard() { | |||
<Banner variant="info"> | |||
<Trans> | |||
<p> | |||
<InfoCircleIcon /> A tech preview of the new {brandName} user | |||
interface can be found <a href="/ui_next">here</a>. | |||
<InfoCircleIcon /> The new user interface can be found{' '} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please don't use "here"
Maybe you the link should be "enable new user interface"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
reworded it, see photo in opening body
@gundalow I just want to know how to use this the first place. I read |
to use
this isn't too different than how it was before, where users had to manually run |
Does this need to go into the contributing/devel docs somewhere? |
Make the newer UI next the default UI experience. Enable legacy ui https://<controller_url>/ui_legacy will redirect to the old user interface Signed-off-by: Seth Foster <fosterbseth@gmail.com>
Signed-off-by: Seth Foster <fosterbseth@gmail.com>
Signed-off-by: Seth Foster <fosterbseth@gmail.com>
Signed-off-by: Seth Foster <fosterbseth@gmail.com>
Signed-off-by: Seth Foster <fosterbseth@gmail.com>
072fed8
to
83666af
Compare
Signed-off-by: Seth Foster <fosterbseth@gmail.com>
I added some documentation on installing the legacy UI |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was able to pull down these changes and walk through the steps provided to successfully build ui_next and then the legacy UI with no issues.
instead of building the ui during make sdist build the ui ahead of time in different docker build stage
Signed-off-by: Seth Foster <fosterbseth@gmail.com>
Signed-off-by: Seth Foster <fosterbseth@gmail.com>
Signed-off-by: Seth Foster <fosterbseth@gmail.com>
Signed-off-by: Seth Foster <fosterbseth@gmail.com>
Quality Gate passedIssues Measures |
no longer plan to serve old UI alongside new UI closing in favor of #15405 |
How to test
make clean-ui ui-devel
make docker-compose
https://localhost:8043/
and login. Should see new UImake target changes
New:
ui-legacy
ui-legacy-release
clean-ui-legacy
Changes (run these OUTSIDE awx containers, requires nodejs >= 18)
ui-devel
- this now makes new UIclean-ui
- cleans new UI filesSUMMARY
Make the newer UI next the default UI experience.
Serves up old UI at
/ui_legacy
pairs with ansible/awx-operator#1923
ISSUE TYPE
COMPONENT NAME
TODO
/ui_legacy/
instead of/