[Freeipa-devel] Daily build of the documentation?

[Rob Crittenden]

Simo Sorce wrote:
> On Tue, 2013-10-29 at 11:03 +0100, Martin Kosek wrote:
>> On 10/29/2013 11:40 AM, Petr Spacek wrote:
>>> On 25.10.2013 17:22, Jérôme Fenal wrote:
>>>> 2013/10/25 Martin Basti <mbasti at redhat.com>:
>>>>> On Fri, 2013-10-25 at 16:48 +0200, Jérôme Fenal wrote:
>>>>>> Hi all,
>>>>>>
>>>>>> Do we have a place where we publish a daily build of the documentation?
>>>>>> I'd like to send such a link for documentation review by Red Hatters.
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>> J.
>>>>>
>>>>> Hi,
>>>>>
>>>>> We don't have place for it yet.
>>>>> IMHO new doc should be published after major corrections.
>>>>> There is a lot of outdated sections which are unusable for freeIPA
>>>>> 3.3.x .
>>>>
>>>> I agree, but it could have the red background "Draft" stamp on it to
>>>> indicate its status.
>>>>
>>>> My goal would be to have it reviewed by Red Hat SAs.
>>>>
>>>> I guess I could also do something internally.
>>>
>>> I think that nightly build with "Draft" stamp is a good idea!
>>>
>>> Martin^1, is it possible to create an 'machine account' with FTP/git access to
>>> some part of freeipa.org? We can run publican from cron and push results to
>>> freeipa.org.
>>>
>>
>> We planned to do exactly this.
>>
>> The problem here is, that in order to the script be able to upload the data, I
>> would need to add it's public key to our FreeIPA.org app and I cannot limit it
>> just to the user guide directory, but it would then have access to the entire
>> wiki gear, write access to git and everything... So question is, if we want to
>> add such access to a public VM in Jenkins or we want to keep it secure in...
>> hm... my notebook.
>
> Maybe we can go the other way around and have a cron job in the
> freeipa.org VM that pulls from a public git tree where the publican
> changes are pushed.

We may not be able to run cron jobs within the gear, but I agree, this 
is a preferrable solution to me too.

rob