search

txty-io / texterify

The translation and localization management system.
https://texterify.com
Other
169 stars 14 forks source link

Download from CLI takes too long and fails #140

Open kas84 opened 1 year ago

kas84 commented 1 year ago

When using the CLI to download like texterify download --project-path public/assets/i18n-texterify sometimes, it is taking like 5-7 minutes or so, other times it just fails.

Would be great if there was a way to check the last version with the CLI so I don't have to download it every time, or you could just cache the export and invalidate it when a new change occurs in a project.

Captura de pantalla 2022-12-19 a las 19 25 47

Any other way on how to integrate this? I was planning on just running the download command every minute, but that doesn't seem feasible.

chrztoph commented 1 year ago

Hey, I will have a look at it why it sometimes fails, but why do you want to fetch the new translations every minute?

kas84 commented 1 year ago

I want to have my translations independent from my code, so I can add a key and immediately (in a minute) deploy it in my code.

Looking at the code, of the export, my bet is the sort because it shouldn't take that long to execute that code. But in any case for me, it makes more sense to execute that code every time the keys or other parameters of the export change, so you download a cached result.

As of right now, we use other tool that integrates with GitHub and I do extactly that... git pull every minute

kas84 commented 1 year ago

Is there a workaround? how do you deploy you i18n files for your projects?

chrztoph commented 1 year ago

It normally doesn't take that long, I will have a look at it. Sorry for the troubles.