I am trying to get Rosey working on a client’s site. The primary issue that I am running into is that the locale files generated as part of the post build step are not being preserved. Before I start trying to mess around trying to figure out work arounds, I look to the community to see if anyone is using Rosey now that the live configuration for sites has gone live.
For the CloudCannon folks, is it best to wait for the v2 of Rosey to release or is it fine to start with v1 and migrate to v2 later.
It sounds like maybe you don’t have the CLOUDCANNON_SYNC_PATHS set? Anything that is generated on the CloudCannon build environment as part of your build only lives in that environment, unless it is synced back to your repository. So I’d guess your locale files are getting generated as part of the postbuild, but not being synced back to your repo to persist between builds.
Does that sound like it could be the culprit?
I would wait for v2 of the Rosey CloudCannon Connector (RCC) - I’m in the final stages of testing it at the moment. You could use Rosey itself now (it’s not waiting on any release) without issue, but if you’d like visual editing of Rosey translation files in CloudCannon, then probably best to wait for v2 of the RCC.
The bulk of the work for setting this all up is usually in the tagging of your HTML with Rosey ids, which is the same whether you use Rosey with or without the RCC. So feel free to start tagging up your HTML in the meantime if you wanted!
I’ll make sure to post a reminder here when v2 is released
folks, is it best to wait for the v2 of Rosey to release or is it fine to start with v1 and migrate to v2 later.