Copr URLs

Pierre-Yves Chibon pingou at
Mon Jun 17 08:59:55 UTC 2013

On , Miroslav Suchý wrote:
> On 06/17/2013 09:30 AM, Bohuslav Kabrda wrote:
> Hi Pierre,
> I've been thinking about this for a long time and this is why I decided 
> to not take your proposed way:
> Since Copr doesn't have control over user names (it takes them from 
> FAS, currently), we cannot prevent user named e.g. "new" or "edit" to 
> register. Since "new" and "edit" are also keywords 
> (/coprs/new/,/coprs/edit/) accessed by GET, this would result in an 
> ugly URL collision (either user's coprs list would be unaccessible or 
> noone would be able to display the "new copr" page).
> Does that make sense or have I missed something?
> Slavek.
> True. What about?
> / > home
> /coprs/details/ > list all the repos (same as home, atm)
> #-----^^^^^^^^^ this is the change
> /coprs/details/<user>/ > list someone's copr
> /coprs/details/<user>/<repo>/ > the detail of this copr
> /coprs/details/<user>/<repo>/{permissions,builds,...}/ > same as now 
> the
> permissions, builds or other page for this repo (the repo file for yum
> could end up here as /coprs/<user>/<repo>/repo/ )

That's also an option :)
But I would argue for using "view" rather than "details".

Then we would have:
/coprs/edit/<user>/          # edit the user info (if/when we have one)
/coprs/delete/<user>/        # delete the user entirely

/coprs/new/<user>/           # create a new repo for this user
/coprs/view/<user>/<repo>/   # view this repo
/coprs/edit/<user>/<repo>/   # edit this repo
/coprs/delete/<user>/<repo>/ # delete this repo


More information about the copr-devel mailing list