A simple solution would be to remove this file from git. What security does
it provide? It only shows "attackers" where is the admin URL, which can be
helpful.

Another option is to simply modify the file on testing.gimp.org. If
robots.txt is not modified, then everything will be fine. If it is modified
at some point (unlikely), git pulling/pushing will fail, which is exactly
what you want, so that you can update the file on testing accordingly.

Your two options sound good too, you just need to make sure that this does
not bite you later on, eg. if the branch name changes or if the git hook is
removed for some other reason.


On Fri, Mar 14, 2014 at 11:05 AM, Michael Schumacher <schum...@gmx.de>wrote:

> Von: "Quentin Pradet" <quentin.pra...@gmail.com>
>
> > Hello,
> >
> > It would probably make sense to put "Disallow: /" in
> http://testing.gimp.org/robots.txt
>
> Yes, good idea.
>
> What is the best way to have this on the testing branch, and never merge
> it back to master by accident:
>
>  - a local git hook on cube to have it create that file on the fly?
>  - a make rule to do this, based on the branch name?
>
>
> --
> Regards,
> Michael
> GPG: 96A8 B38A 728A 577D 724D 60E5 F855 53EC B36D 4CDD
> _______________________________________________
> gimp-web-list mailing list
> gimp-web-list@gnome.org
> https://mail.gnome.org/mailman/listinfo/gimp-web-list
>
_______________________________________________
gimp-web-list mailing list
gimp-web-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-web-list

Reply via email to