hexylena
commented
1 year ago https://github.com/usegalaxy-eu/infrastructure-playbook/blob/master/templates/nginx/galaxyproject.j2 it's all here. Just make a PR with whatever you want to redirect.
Open NickSto opened 1 year ago
hexylena
commented
1 year ago https://github.com/usegalaxy-eu/infrastructure-playbook/blob/master/templates/nginx/galaxyproject.j2 it's all here. Just make a PR with whatever you want to redirect.
NickSto
commented
1 year ago @hexylena Perfect, thank you. That explains why everything showed galaxyproject.eu being pointed at an independent host.
I made the PR (usegalaxy-eu/infrastructure-playbook#421) and they're pretty simple redirects but my nginx memory is stale so feel free to correct me.
bgruening
commented
1 year ago Why does this not point to the usegalaxy.org page? I thought this was the idea so that we can start writing posts only in ORG? Same for events.
| .eu page | 301 redirect to | notice? |
|---|---|---|
| galaxyproject.eu/news | usegalaxy-eu.github.io/eu/news/ | notice |
| galaxyproject.eu/pasteur/news | usegalaxy-eu.github.io/pasteur/news/ | notice |
I guess those make sense since they are not yet ported?
| .eu page | 301 redirect to | notice? |
|---|---|---|
| galaxyproject.eu/tools | usegalaxy-eu.github.io/tools | |
| galaxyproject.eu/freiburg/jobs | usegalaxy-eu.github.io/freiburg/jobs |
For those we need to create a list of all important posts and establish a redirect, but why point to the github.io URL and not the galaxyproject.org URL with the ported post?
| .eu page | 301 redirect to | notice? |
|---|---|---|
| galaxyproject.eu/posts/2018/10/08/gxadmin/ | usegalaxy-eu.github.io/posts/2018/10/08/gxadmin/ |
NickSto
commented
1 year ago @bgruening
Why does this not point to the usegalaxy.org page? I thought this was the idea so that we can start writing posts only in ORG? Same for events.
galaxyproject.org/eu/news/ currently has the last 3 months of news. galaxyproject.eu/news has the last 5 years. If we automatically redirect people away from galaxyproject.eu/news, the page becomes inaccessible. Then they won't be able to go back and find any news posts older than 3 months. Adding the notice lets people know where to go for new posts, but it lets them reference old ones if they need to. Then we can start posting only to .org.
For those we need to create a list of all important posts and establish a redirect, but why point to the github.io URL and not the galaxyproject.org URL with the ported post?
galaxyproject.eu/posts/2018/10/08/gxadmin/ is an example of a post that hasn't been ported yet. For posts that have been ported, I agree we should redirect users to the post on .org.
The galaxyproject.org Global Hub project is nearly ready for launch. The galaxyproject.eu homepage, its news and events feeds, and those of its member sites, are all up and running at .org now. We're still working on migrating old pages and posts over, but for now we're just pointing to the pages on .eu.
We'd like to launch soon, so that authors will be able to start taking advantage of features like easy cross-posting between communities. For instance, a lot of announcements are applicable to both the US and EU communities. Once we launch, we'll be able to make one post and add US and EU tags instead of creating two separate posts, one for each site.
With that in mind, I'd like to discuss how to begin the transition. Last we spoke, @bgruening was interested in just redirecting the main galaxyproject.eu/ homepage to galaxyproject.org/eu/, then have some links back to the usegalaxy-eu.github.io versions for pages that aren't migrated yet. I think this would mean a redirect on every page with a news/events feed (see here for my list of such pages). But I'm not sure the best method of redirection, since I'm not familiar with the hosting environment. Should it be a 301 from the server? Or a meta refresh or some Javascript?
And if you have any feedback on any aspect of the plan, please don't hesitate to give it.
Examples
Just to make sure we're on the same page, here are some examples pages and what will be done with them. This is what I understand the plan to be, but let me know if people disagree. (This is covered in general in https://github.com/galaxyproject/galaxy-hub/issues/1480#issuecomment-1170362963 but examples might help.)
The "notice" ones will have a banner placed at the top of the destination page (the second column) warning about the migration, with a link to where to find the rest of the content.
Note: Ideally if a post has already been migrated to .org, we'd redirect the visitor there. But we can't list every news/event post in the nginx config. Maybe we could do it by adding a
redirectmetadata field to pages, like on .org.Also, FYI, the urls on .org won't all be the same as on .eu, so even once everything is migrated, a simple site-wide 301 wouldn't work. The urls won't be the same for a few reasons. One is that the url structure is different, e.g.
/news/2018-10-08-gxadmin/instead of/posts/2018/10/08/gxadmin/. Also, .org doesn't allow uppercase or certain special characters in urls, soPapercuts_Januarybecomespapercuts-january,de.STAIRbecomesde-stair, andfeatureCountsbecomesfeature-counts.