Skip to content

Conversation

@exmatrikulator
Copy link

No description provided.

@jbruechert
Copy link
Collaborator

Thanks!

It looks like this breaks running outside of docker though, right?
Generating the config file is definitely something we need, but I think we should we should try to have the docker image replicate the setup on the server as much as possible, so the config file can be exactly the same. That means motis in the docker image needs to go into /opt/motis/

I can make those changes if you want.

@exmatrikulator
Copy link
Author

I know, I saw the same problem(s).
Ansible is great, but I can't use it on my dev environment and it's hard to learn the first motis steps with this.
Yes, with docker there will be 2 option to run it and you have 2 options to maintain :(
No, the Ansible way should work as well.
It's not only the montis install path which is different, also the splitting ini.

I liked the idea that you can easy run a docker-compose with example data from Aachen out of the box.
The data is stored in volume and can be replaced by the europe.pbf and other feeds without changing the setup.

I needed it for my setup to look into motis, so I wanted to share it with you.
Maybe this is another/better way to deploy it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants