|
If my rails port and tile server built on two different hosts, called s1 and s2. Now i make an edit at the openstreetmap database on s1, can i use the render_expired command on the s1 host to updata tiles on the s2 host? If it is feasible, how to set the config to make render_expired command renderd the specifiled host and database? |
|
You'd need to write some code to do that, I think. The usual mechanism (with a rendering server consuming diffs from OSM.org) is:
That process means that data that has changed on the rails port is used to update the rendering server database and the rendering server can choose to expire (or rerender) the affected tiles. Given that the rails port and rendering server are separate databases anyway, and you'll need to do something to get changed data from one into the other (such as processing diffs) why not just use those diffs to drive rerendering? I'm sure it would be technically possible to link rerendering to editing instead, but it doesn't actually achieve anything different in the long run. If it helps, I have variations on tile expiry scripts here and here that have a few more comments explaining tile expiry usage. Sorry, i didn't express well. The rails port and rendering server are separate databases, they also built on separate host, the rails port on the s1 host, and rendering server on the s2 host, can i use the render_expired command on the s1 host to updata tiles on the s2 host?
(31 Dec '16, 12:08)
yuyy
Not easily - it communicates with the renderer via a socket. Easier to get the list of tiles from s1 to s2 and run render_expired on s2.
(03 Jan '17, 13:03)
SomeoneElse ♦
|
