Where do we want to put pagure?

[Pierre-Yves Chibon]

Good Morning Everyone,

As pagure over dist-git is coming closer and closer I realized we didn't talk
about the most important part of the project: where do we want to put it?

In stg I put it under src.stg.fp.o/pagure so it stands nicely on the side of
everything else on the server and to be sure it is not going to conflict.
But, do we want to follow the same path in production or do we want to deploy it
at src.fp.o/ directly?

Thoughts?


Pierre

[Randy Barlow]

On Tue, 2017-08-01 at 22:23 +0200, Pierre-Yves Chibon wrote:
>  But, do we want to follow the same path in production or do we want
>  to deploy it
>  at src.fp.o/ directly? 
I like src.fpo.o aesthetically, but don't have a technical argument one
way or the other.

[Kevin Fenzi]

On 08/01/2017 01:44 PM, Randy Barlow wrote:
>  On Tue, 2017-08-01 at 22:23 +0200, Pierre-Yves Chibon wrote:
> > But, do we want to follow the same path in production or do we want
> > to deploy it
> > at src.fp.o/ directly?
>  
>  I like src.fpo.o aesthetically, but don't have a technical argument one
>  way or the other. 
I like putting it at / but we do have some stuff at /lookaside/ and
/cgit (going away?). So I suppose best might be redirecting / to /pagure
and dropping cgit?

kevin

[Pierre-Yves Chibon]

On Tue, Aug 01, 2017 at 06:21:21PM -0700, Kevin Fenzi wrote:
>  On 08/01/2017 01:44 PM, Randy Barlow wrote:
>  > On Tue, 2017-08-01 at 22:23 +0200, Pierre-Yves Chibon wrote:
>  >> But, do we want to follow the same path in production or do we want
>  >> to deploy it
>  >> at src.fp.o/ directly?
>  > 
>  > I like src.fpo.o aesthetically, but don't have a technical argument one
>  > way or the other.
>  
>  I like putting it at / but we do have some stuff at /lookaside/ and
>  /cgit (going away?). So I suppose best might be redirecting / to /pagure
>  and dropping cgit? 
So I looked at this this morning, we can put pagure in / and keep /lookaside
(and even /cgit) working
cf:
https://src.stg.fedoraproject.org/lookaside
https://src.stg.fedoraproject.org/cgit
https://src.stg.fedoraproject.org/

The issue is with this last one, we have in our apache conf:
    RedirectMatch permanent ^/$ https://src.fedoraproject.org/cgit/

(also in stg, so stg redirects to prod there, but it works, using curl you'll
get the pagure page)

So, how long does it take for a browser to forget about a 301 code?
I think we can break the look by introducing an infinite loop that will make the
force the browser to recheck the original 301 but that means putting a redirect
from cgit to pagure which effectively answers the question of whether we want to
drop cgit or not.

If we move the redirect from / to /pagure we will face the same 301 redirect
issue that the browser has cached.

More ideas/thoughts?


Pierre

[Matthew Miller]

On Tue, Aug 01, 2017 at 10:23:13PM +0200, Pierre-Yves Chibon wrote:
>  In stg I put it under src.stg.fp.o/pagure so it stands nicely on the
> side of
>  everything else on the server and to be sure it is not going to conflict.
>  But, do we want to follow the same path in production or do we want to deploy it
>  at src.fp.o/ directly? 
Are there other things we might want want to put at the top level, or
at other levels with the same top URL? Documentation? Actual exploded
source trees? If not, top level seems fine. If so, do we want to use
the name of the software ("pagure") or something descriptive (like
"dist-git", even if that's mainly descriptive to packagers?).

(Unrelated: the banner in stg has "fedora PAGURE" at the top. Is there
a design ticket for a dist-git banner?)


-- 
Matthew Miller
<mattdm(a)fedoraproject.org&gt;
Fedora Project Leader

[Dusty Mabe]

On 08/01/2017 04:50 PM, Matthew Miller wrote:
>  On Tue, Aug 01, 2017 at 10:23:13PM +0200, Pierre-Yves Chibon wrote:
> > In stg I put it under src.stg.fp.o/pagure so it stands nicely on the side of
> > everything else on the server and to be sure it is not going to conflict.
> > But, do we want to follow the same path in production or do we want to deploy it
> > at src.fp.o/ directly?
>  
>  Are there other things we might want want to put at the top level, or
>  at other levels with the same top URL? Documentation? Actual exploded
>  source trees? If not, top level seems fine. If so, do we want to use
>  the name of the software ("pagure") or something descriptive (like
>  "dist-git", even if that's mainly descriptive to packagers?).
>  
>  (Unrelated: the banner in stg has "fedora PAGURE" at the top. Is there
>  a design ticket for a dist-git banner?)
>  
>   
Any reason we can't make it a "group" within the other pagure at pagure.io?

pagure.io/dist-git/rpms/
pagure.io/dist-git/containers/

Dusty

[Peter Robinson]

>  On 08/01/2017 04:50 PM, Matthew Miller wrote:
> > On Tue, Aug 01, 2017 at 10:23:13PM +0200, Pierre-Yves Chibon wrote:
> >> In stg I put it under src.stg.fp.o/pagure so it stands nicely on the side of
> >> everything else on the server and to be sure it is not going to conflict.
> >> But, do we want to follow the same path in production or do we want to deploy it
> >> at src.fp.o/ directly?
> >
> > Are there other things we might want want to put at the top level, or
> > at other levels with the same top URL? Documentation? Actual exploded
> > source trees? If not, top level seems fine. If so, do we want to use
> > the name of the software ("pagure") or something descriptive (like
> > "dist-git", even if that's mainly descriptive to packagers?).
> >
> > (Unrelated: the banner in stg has "fedora PAGURE" at the top. Is there
> > a design ticket for a dist-git banner?)
> >
> >
>
>  Any reason we can't make it a "group" within the other pagure at pagure.io?
dist-git is currently different infrastructure, I'm not even sure if
pague.io is hosted in the same DC/network.

I like the root src.fp.o/ idea, adding the extra pagure/ just seems
like extra characters for no extra benefit.

Peter

[Patrick マルタインアンドレアス Uiterwijk]

>  dist-git is currently different infrastructure, I'm not even sure
> if
>  pague.io is hosted in the same DC/network. 
It is not. Pagure.io is hosted in OSUOSL, while dist-git and all build infra is in PHX2.

>  
>  I like the root src.fp.o/ idea, adding the extra pagure/ just seems
>  like extra characters for no extra benefit. 
Agreed, let's put it on the root.
Please do make sure that /git/$namespace/$name.git and /cgit/$namespace/$name.git both
keep working for git checkouts.
We've got multiple people that have used the /cgit as git checkout path, and breaking
clones for them would be not nice.

[Matt Prahl]

I think src.fp.o/ is perhaps the better option. If you want to be cautious and keep the
base url reserved for some future use, you can redirect src.fp.o/ to src.fp.o/pagure/,
although I don't see a reason to do so.

[Jeremy Cline]

On 08/01/2017 09:13 PM, Matt Prahl wrote:
>  I think src.fp.o/ is perhaps the better option. If you want to be
> cautious and keep the base url reserved for some future use, you can redirect src.fp.o/ to
> src.fp.o/pagure/, although I don't see a reason to do so. 
I'd prefer stage and prod to be as close as possible to identical. Also
people have been writing patches with the assumption that it'll be
src.fedoraproject.org/pagure/[0]. It's not hard-coded, but it is the
setting default if unspecified.

A redirect would be fine, in my opinion.

[0]
https://github.com/fedora-infra/fmn/pull/206/files#diff-9113aa22121415ee9...


-- 
Jeremy Cline
XMPP: jeremy(a)jcline.org
IRC:  jcline

[Patrick マルタインアンドレアス Uiterwijk]

>  On 08/01/2017 09:13 PM, Matt Prahl wrote:
>  
>  I'd prefer stage and prod to be as close as possible to identical. Also
>  people have been writing patches with the assumption that it'll be
>  src.fedoraproject.org/pagure/[0]. It's not hard-coded, but it is the
>  setting default if unspecified. 
They should indeed be identical, so let's move both.
If that needs code changes, so be it.
Please do make sure that you test pagure and lookaside and both https git urls in staging
before moving to prod.

> 
> A redirect would be fine, in my opinion.
> 
> [0]
> https://github.com/fedora-infra/fmn/pull/206/files#diff-9113aa22121415ee9...