[FFmpeg-devel] fateserver maintaince

[Michael Niedermayer]

On Sat, Jan 18, 2014 at 12:33:09PM -0800, Timothy Gu wrote:
> On Sat, Jan 18, 2014 at 11:28 AM, Michael Niedermayer <michaelni at gmx.at> wrote:
> > Hi all
> >
> > as we now have a patch against fateserver on the list, we need a
> > maintainer for fateserver.
> > That is someone to review such patches, make sure they have been
> > tested (either by the author or maintainer) and that they get applied
> > to git and end on fate.ffmpeg.org if they are ok
> >
> > I am not the ideal person for this as my perl knowledge is rather
> > basic.
> 
> First, I am not the ideal person either as I know absolutely no perl
> (my patch is just copy-paste).
> 

> Second, can someone provide info on how to test fateserver? #

iam not sure whats the easiest way for a contributor to test locally
but you will need apache or something equivalent running with cgi
execution allowed.

normally for a actual server you would setup a user and sshd to get
data from clients but suspect this isnt neccessary and things can
be shortcut somehow

> How does
> the FATE* envvar work?

FATE_USER / FATEDIR would be set by .ssh/authorized_keys based on
the public key of the client but i guess it can be shortcut and done
more directly



> 
> Third, if testing on contributor machine is not realistic, then can
> someone create a fatetest.ffmpeg.org?

i could create the subdomain if someone wants to setup such a fatetest


> 
> BTW, is it realistic to create a fatesever FATE test?

i guess anything is possible, but it doesnt seem very easy

[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

If you think the mosad wants you dead since a long time then you are either
wrong or dead since a long time.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://ffmpeg.org/pipermail/ffmpeg-devel/attachments/20140118/d583ba10/attachment.asc>