Hi

Dne 18.5.2016 v 09:58 Pau Rul·lan Ferragut napsal(a):
> At work we are deploying an internal weblate for our customers and
> projects. This instance is deployed on a kubernetes cluster where I am
> having trouble of managing the DATA_DIR volume and the maintenance cron
> jobs.
> 
> The problem is that Google's persistent disks only allow a single
> writer. I will not be able to launch more than a pod but I can live with
> that.
> The big consequence is that I cannot create another django instance for
> the crons. To remedy this I have been thinking to add an REST endpoint
> to launch the different commands (something like
> `/api/maintenance/cleanuptrans` and so on).

Having maintenance tasks in the API is planned, though it's currently
not fixed on roadmap. I suggest you to open issue in our issue tracker,
so that your specific needs will be addressed when this will be implemented.

> 1. How do you manage the DATA_DIR for the hosted version?

Hosted Weblate is running on regular KVM guest, so there is no problem
with that.

> 2. How do people deploy multiple weblate instances and share the DATA_DIR?

Not sure, it's probably not needed unless you use Docker with single
process in container policy...

> 3. Is there any workaround for my situation?
> 4. Does adding a REST endpoint sound like a good idea?
> 5. If I develop the endpoints, would you add it to the weblate repo?

Yes, we definitely accept pull request. I recommend you to first discuss
design of the API (probably issue tracker is better place than this list).

-- 
        Michal Čihař | http://cihar.com/ | https://weblate.org/

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
Weblate mailing list
[email protected]
https://lists.cihar.com/cgi-bin/mailman/listinfo/weblate

Reply via email to