Opened 9 years ago
Closed 9 years ago
#14 closed task (fixed)
Establish HTTP redirect to GitLab for /project/.../<repository>
Reported by: | ehuelsmann | Owned by: | somebody |
---|---|---|---|
Priority: | major | Milestone: | |
Component: | component1 | Version: | |
Keywords: | Cc: | ||
Parent Tickets: | 12 |
Description
Attachments (1)
Change History (6)
comment:1 Changed 9 years ago by
comment:2 Changed 9 years ago by
Every repository in the listing at https://common-lisp.net/gitlab-migration-repository-mapping/ needs a rewrite rule like the one below (which I tested and works):
# For the repository originally located at physical path /project/oct/public_html/git/oct.git RewriteRule ^/project/oct/git/(oct.git.*)$ https://gitlab-test.common-lisp.net/oct/$1
comment:3 Changed 9 years ago by
Next step is to attach a full listing of rewrite rules to be included in the common-lisp.net:443 virtual host block. The one above was inserted - for testing purposes - above these lines within said block:
AliasMatch ^/projects/([^/]+)(.*) /srv/project/$1/public_html/$2 AliasMatch ^/project/([^/]+)(.*) /srv/project/$1/public_html/$2 AliasMatch ^/p/(.*) /srv/project/$1
comment:4 Changed 9 years ago by
Please note that in said listing, there are some URLs in the users' namespace as well (e.g. https://common-lisp.net/~frideau/...). These too need redirects using the same redirect pattern, using the name of the user instead of the name of the project.
Changed 9 years ago by
Attachment: | rewriterules added |
---|
Rewrite rule example such as generated during migration
comment:5 Changed 9 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
With the implementation of the rewrite rules above, I'm considering this task done. Closing as fixed.
Purpose of the redirect is to keep being able to check out published repositories over HTTP(S).