base_app_url not behaving as expected

[HolgerNetgrade]

Hi,
I've setup a Cronicle instance to be accessible from https://my.domain.tld/cronicle.
I set the base_app_url to be exactly this URL.

Now unfortunately Cronicle frontend still queries its assets and API without the /cronicle/ part.
For instance, it tries to load
https://my.domain.tld/api/app/config
instead of
https://my.domain.tld/cronicle/api/app/config
resulting in a 404.

I did a /opt/cronicle/bin/control.sh restart after editing the config.

Did I miss something, or could ti be that URLs like this are currently not supported?

[dheise-rheinenergie-trading-com]

Cronicle has no support for the usage of a context root like your /cronicle/....

[HolgerNetgrade]

I see, thanks!

[mikeTWC1984]

@HolgerNetgrade yeah, it's not a feature of cronicle. However it can be achieved with some nginx hacks, search for nginx in issues, I htink this was discussed few times, I recall I posted some sample configs.
You can also try my fork, I added that feature.
https://github.com/cronicle-edge/cronicle-edge/releases/tag/v1.10.1

[HolgerNetgrade]

Oh, that's cool. I might try out your Cronicle Edge.
do you think it should work out if I just overwrote the files of an existing Cronicle installation with the contents of dist after building edge?

[mikeTWC1984]

Typically I'd suggest just to export your metadata from old cronicle storage-cli.js export
then spin up edge, go to schedule, click import button and copy the export output there. I think copying over data folder might work too, but you will likely face some quirks