<br><br><div class="gmail_quote">On Thu, Oct 13, 2011 at 3:17 PM, Kevin Fenzi <span dir="ltr"><<a href="mailto:kevin@scrye.com">kevin@scrye.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Thu, 13 Oct 2011 13:27:13 +0200<br>
Kévin Raymond <<a href="mailto:shaiton@fedoraproject.org">shaiton@fedoraproject.org</a>> wrote:<br>
<br>
> Hi guys,<br>
><br>
> Currently the script run hourly to build our website is pulling all<br>
> translations.<br>
> I would like to add a commit/push then, in order to track each PO<br>
> updates. That would ensure for us to do it frequently (currently I do<br>
> it manually times to times) and would be faster for us to checkout<br>
> them (pulling from Transifex is really slow).<br>
<br>
</div>A push from the script?<br>
<br></blockquote><div><br>I think Kevin R. is referring to a job that pull from tx regularly and pushes it to the fedora-web.git repo. The idea is that the hourly website build job wouldn't have to pull *all* the data from tx just the changed ones from the other [tx pull commit to fedora-web.git] job. This would hopefully make the build times faster.<br>
</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
...snip...<br>
<div class="im"><br>
> Please, note that I have really no idea if pushing from there is<br>
> allowed, even if this is working. It is not the aim of a production<br>
> server… Should we add a cron somewhere?<br>
> Do you see the advantage of this?<br>
<br>
</div>I don't think there's any permissions there to push. It's running as<br>
the apache user, and I don't think it's a good idea to set it up to<br>
commit. If someone broke into that account they could push bad changes<br>
back to the repo. This seems like not a good idea.<br><div> </div></blockquote><div><br>We were able to do this commit process when Fedora was running their own TX instance. Once it was upgraded that functionality disappeared.<br>
<br> <br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div> </div></blockquote><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">
> I also though of a way to update POT frequently.<br>
> Couldn't we push the pot at each rebuild from the master?<br>
> All major changes would always be in an other branch, right? Therefore<br>
> there should be no way to avoid POT change from master (from the<br>
> translator side). A daily job would also do it.<br>
><br>
> Here find as attachment a patch proposal (please mind that I wrote it<br>
> without test and that I am not a bash guru)<br>
<br>
</div>Perhaps some kind of daily job somewhere else...<br>
or perhaps someone could just do it every week or more regularly.<br>
<br>
I'd be happy to do it if I knew the exact SOP/process to do so.<br>
<font color="#888888"><br>
kevin<br>
</font><br></blockquote><div><br>Kevin F. I hope this clears a couple of things up.<br><br>Sijis<br></div></div><br>