[Sozo] Force deploying new World about dojo HOT 7 CLOSED

came here to say the same thing :)

from dojo.

You're the 🐐 sir, thanks

from dojo.

@kariy rather then generating a random salt, lets have the user provide a world name which we can hash to the salt. in some cases, the user will want to run migrate against an existing world, to install new components / systems for example

from dojo.

@kariy rather then generating a random salt, lets have the user provide a world name which we can hash to the salt.

perhaps it's better if we just have a --salt option for sozo migrate? name doesn't seem very intuitive

from dojo.

@kariy rather then generating a random salt, lets have the user provide a world name which we can hash to the salt.

perhaps it's better if we just have a --salt option for sozo migrate? name doesn't seem very intuitive

i like name since it abstracts the underlying implementation detail and is easily communicated. i think it is more intuitive, since without a pretty deep understanding of deployments, it's not clear what salt refers to. in the future, we can also use the name as world metadata

for example, a developer might want to modify realms world:

sozo migrate --name realms

in the future, there might be names that dont fit into 31bytes, like

sozo migrate --name world_of_warcraft_burning_crusade

in which case, we need to hash it, so we're breaking the users expectations of how the salt will be used in that case and it makes sense to have our own concept

from dojo.

i like name since it abstracts the underlying implementation detail and is easily communicated. i think it is more intuitive, since without a pretty deep understanding of deployments, it's not clear what salt refers to.

make sense

in the future, we can also use the name as world metadata

aight

from dojo.

Resolves in #654

from dojo.