[
https://issues.apache.org/jira/browse/ARTEMIS-5440?focusedWorklogId=968285&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-968285
]
ASF GitHub Bot logged work on ARTEMIS-5440:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 01/May/25 09:31
Start Date: 01/May/25 09:31
Worklog Time Spent: 10m
Work Description: grgrzybek commented on PR #82:
URL:
https://github.com/apache/activemq-artemis-console/pull/82#issuecomment-2844505928
> @grgrzybek about the .env file - the only value beling replaced by webpack
is PUBLIC_URL, and it's "hardcoded" into the webpack.config.cjs:
>
> ```
> new InterpolateHtmlPlugin(HtmlWebpackPlugin, {
> PUBLIC_URL: '/console'
> }),
> ```
>
> I don't think the .env file is used anywhere (I don't know webpack all
that well), and if it is, it's redundant with this configuration anyway. Can
you check and possibly remove the file?
>
> And if the link will always stay the same in index.html,
InterpolateHtmlPlugin only unnecessarily makes things more complex. It would
suffice to change the PUBLIC_URL to /hawtio in the index.html itself.
you're right - I'm not 20+ year experienced in JS, this ecosystem changes
every year. My initial contribution was about moving from Craco to extracted
(ejected) webpack - this broke the tests, but we had to do it because Craco is
[officially
deprecated](https://react.dev/blog/2025/02/14/sunsetting-create-react-app).
{{.env}} file was used with Craco, but isn't with webpack. Let's improve
this JS code iteratively learning along the way ;)
Issue Time Tracking
-------------------
Worklog Id: (was: 968285)
Time Spent: 40m (was: 0.5h)
> New Artemis Management Console not working under custom context path
> --------------------------------------------------------------------
>
> Key: ARTEMIS-5440
> URL: https://issues.apache.org/jira/browse/ARTEMIS-5440
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Web Console
> Affects Versions: 2.40.0
> Reporter: Lucian Burja
> Priority: Major
> Labels: pull-request-available
> Attachments: console.png, screenshot-1.png, screenshot-2.png
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> In our organisation we're running the ActiveMQ Artemis Management Console
> under a custom context path (i.e., {{/artemis/console}}).
> In {{etc/bootstrap.xml}} we configure it like this:
> {code:xml}
> <web bind="http://0.0.0.0:8161"; path="web">
> <app url="artemis/console" war="console.war"/>
> </web>{code}
> This setup works as expected in version 2.38.0 but fails in 2.40.0
> In 2.40.0 when accessing the console I see that:
> * The browser correctly redirects to {{/artemis/console/login}}
> * However, the loaded HTML sets the {{<base href>}} to {{/console/}} instead
> of {{/artemis/console/}}
> !console.png|width=1000!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact
