Retrigger build on OSM pbf update

[Bryze]

I have tried the following approach to trigger an rebuild/update.

• Replaced the OSM file manually and executed docker restart <container> command.

I receive the following output on restart:

2024-04-02 12:27:02 find: '/custom_files/transit_tiles': No such file or directory
2024-04-02 12:27:02 INFO: Found routing tiles with 'use_tiles_ignore_pbf' True.
2024-04-02 12:27:02 INFO: Jumping directly to the tile loading!
2024-04-02 12:27:02 INFO: Found existing valhalla.json. Updating possibly missing entries.
2024-04-02 12:27:06 WARNING: User valhalla is running with sudo privileges. Try building the image with a host user's UID & GID.
2024-04-02 12:27:09 INFO: Found config file. Starting valhalla service!
2024-04-02 12:27:09 2024/04/02 06:57:09.993200 [INFO] Tile extract successfully loaded with tile count: 5585
2024-04-02 12:27:09 2024/04/02 06:57:09.994018 [INFO] Tile extract successfully loaded with tile count: 5585
2024-04-02 12:27:09 2024/04/02 06:57:09.994128 [INFO] Tile extract successfully loaded with tile count: 5585

Does it indicate that the build has been updated and will serve the data wrt the new OSM file?

---

Also, I'm a bit confused by the following line in the documentation: Supports auto rebuild on OSM file changes through hash mapping.

Few questions:

• Does it mean that there's no need to restart the docker container? And we can just keep on updating the OSM files manually?

(apologies if it's too basic, I wasn't sure where to check/ask this)

[nilsnolde]

2024-04-02 12:27:02 INFO: Found routing tiles with 'use_tiles_ignore_pbf' True.

from the docs:

use_tiles_ignore_pbf: True uses a local tile.tar file and skips building. Default True.

and

Upon docker restart <container> those changes are taken into account via hashed files, and, if necessary, new graph tiles will be built automatically.

yes, you'll need to restart.