Your approach might work. However, currently Mendix does not officially support apps running at URLs beyond the root level. Instead the standard recommendation is to use different subdomains for each app. So instead of:
you should use:
If that’s definitely not an option, you can still make most things work. One exception I know of is the built-in page URL feature.
Runtime settings in the docker buildpack are used by setting an environment variable with a prefix, so:
and the value should be the actual URL of the application.
Thanks Eric for the response :)
I tried to deploy my mendix application and provide the “MXRUNTIME_ApplicationRootUrl” as an enviroment variable. (see docker-compose bellow) Unfortunately, it didn’t help.
I have some other ideas how to solve it but I am not very optimistic.
version: '2.4' services: myapp: environment: ADMIN_PASSWORD: Password DATABASE_ENDPOINT: 'jdbc:hsqldb:file:~/data/database/db:mem:mendix' MXRUNTIME_DatabaseType: HSQLDB MXRUNTIME_DatabaseJdbcUrl: 'jdbc:hsqldb:file:~/data/database/db:mem:mendix' MXRUNTIME_ApplicationRootUrl: 'https://192.168.239.129/myapp' image: 'mendixblank/mendixnews:blank' mem_limit: 1gb restart: unless-stopped ports: - '8080'
I have come across the same scenario as you did earlier today. I have tried following the documentation here – https://github.com/mendix/m2ee-tools/blob/master/examples/full-documented-m2ee.yaml (which is simply putting ApplicationRootUrl as the setting) but it didn't work for me some reason. I have tried Eric's method and it didn't work for me either.
Then I came across this post – https://forum.mendix.com/link/questions/102794 and this guy did the same as I did and it worked. So I tried again and it worked for me! I hope it helps you too! Joy