Skip to content
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

Deploying ORS 6.8.3 is only loading ors-config.json when tomcat resides in a volume. #1930

Open
1 task done
jannefleischer opened this issue Dec 11, 2024 · 0 comments
Open
1 task done

Comments

@jannefleischer
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Problem description

I moved our deployment of ors to a new server, hence I needed to redeploy everything, except I had well calculated graphs and a working configuration.

Since I couldn't find a documentation for 6.8.3 (at first...its only available in git) I just ran sudo docker compose up -d and hoped for the best. When starting it (without building it myself) the docker-entrypoint.sh realized there is a config file in /home/ors/ors-conf and copies it to /home/ors/ors-core/ors-config.json. Then it deploys the ors.war - BUT the .war file doesn't seems to recognize there is the config file it should work with and instead starts with the default location /home/ors/tomcat/webapps/ors/WEB-INF/classes/ors-config.json. Therefore only a default profile is loaded.

Only when I made sure tomcat is deployed into a persistent volume (or in my case a bind [after using docker cp ors:/home/ors/tomcat ./tomcat]) at least on second run of my docker compose up -d my config is used and my existing graphs are loaded.

Proposed solution

So, since 6.8.3 is quite old I don't expect this to be fixed, but wanted to let people know who might struggling with this, that there migh be an issue (and what might be a solution).

Additional context

There are issues raised before that are similiar. I think they are somewhat fixed, but don't know the specifics:
#742, #745.

Forum Topic Link

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant