Looks easy to back out. +1
On 22 April 2016 at 11:35, Pierre-Yves Chibon <pingou@xxxxxxxxxxxx> wrote:
> Hi all,
>
> The possibility to keep the URL backward compatible in pagure 2.0 is an option
> that is off by default.
> I would like to apply the following change to pagure's configuration file to
> turn it on.
>
> diff --git a/ roles/pagure/frontend/templates/pagure.cfg b/ roles/pagure/frontend/templates/pagure.cfg
> index 77cfdfc..2748861 100644
> --- a/ roles/pagure/frontend/templates/pagure.cfg
> +++ b/ roles/pagure/frontend/templates/pagure.cfg
> @@ -196,3 +196,10 @@ SSH_KEYS = {
> }
> }
> {% endif %}
> +
> +# Allow the backward compatiblity endpoints for the old URLs schema to
> +# see the commits of a repo. This is only interesting if you pagure instance
> +# was running since before version 1.3 and if you care about backward
> +# compatibility in your URLs.
> +OLD_VIEW_COMMIT_ENABLED = True
> +
>
> The change is already done manually in stg so that we could check that it is
> working, but I would like to apply it in ansible for both stg and prod since it
> will not have any impact for prod until we upgrade to 2.0.
>
> +1s?
>
> Thanks,
> Pierre
>
> _______________________________________________
> infrastructure mailing list
> infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
> http://lists.fedoraproject.org/admin/lists/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
>
--
Stephen J Smoogen.
_______________________________________________
infrastructure mailing list
infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
http://lists.fedoraproject.org/admin/lists/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
