Why don't we ship osrm-backend profiles in node-osrm?
node-osrm ships osrm-backend binaries such as osrm-extract and osrm-contract which need to be run for making use of node-osrm. We recommend using the binaries shipping with node-osrm since it's easier to use and the chances for a version mismatch are non-existent.
But then why don't we ship profiles (i.e. car.lua and all Lua modules we require) needed for running osrm-extract? Having the user manually grab profiles from the osrm-backend repo. is not particularly user-friendly.
Can't we just ship profiles along the binaries to get a working setup out of the box?
Why don't we ship osrm-backend profiles in
node-osrm?node-osrmshipsosrm-backendbinaries such asosrm-extractandosrm-contractwhich need to be run for making use ofnode-osrm. We recommend using the binaries shipping withnode-osrmsince it's easier to use and the chances for a version mismatch are non-existent.But then why don't we ship profiles (i.e.
car.luaand all Lua modules we require) needed for runningosrm-extract? Having the user manually grab profiles from theosrm-backendrepo. is not particularly user-friendly.Can't we just ship profiles along the binaries to get a working setup out of the box?