Understanding UUID pitfalls when sharing content among servers

[lukasbestle]

@plagasul

When you say “run the migration” you imply aswell to force the generation of all UUID, correct?

That’s what I mean with the migration.

@plagasul

And, if I understand you correctly, if all uuid are generated, say, in server A, then I dowload content and create new pages, upload files, etc in server B, UUID are also generated for all those elements, and I can upload them to server A again, as they will not cause any collision or any kind of problem?

This assumes that uuid are generated on page, file… creation, is this correct ?

That’s exactly right. Kirby automatically generates UUIDs for every newly created page and file. These UUIDs will then be uploaded back to server A together with your changed and added content.

Because the length and character set of the UUIDs is quite large and the source for random data is the best that PHP offers, the collision probability is so low that collisions throughout dozens of years of normal use of Kirby are not to be expected. That’s independent from whether you use one or multiple servers.