Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Links and search results for Lagoon CLI documentation return HTTP 404 Not Found #201

Open
christopher-hopper opened this issue Oct 5, 2021 · 2 comments

Comments

@christopher-hopper
Copy link

Describe the bug

Search for Lagoon CLI documentation and many results in the first page return a 404 Not Found.

Links in other people's documentation also return a 404 Not Found.

To Reproduce

Steps to reproduce the behavior:

  1. Go to Google, Bing or "some other search engine"
  2. Type keywords "Lagoon CLI"
  3. Click on numerous links in the results, or second-tier links in pages.
  4. See an error page at https://amazeeio.github.io/lagoon-cli/

Expected behavior

A redirect takes me to the new documentation site at https://uselagoon.github.io/lagoon-cli/

Additional context

A method for redirecting github pages after a repository move is described in this Gist
https://gist.github.com/domenic/1f286d415559b56d725bee51a62c24a7

Hopefully it helps.

@tobybellwood
Copy link
Member

tobybellwood commented Oct 5, 2021

I've just remembered why we didn't do that method...

I'm not sure of the impact it would have on other Github pages-hosted sites in the amazeeio namespace (eg https://amazeeio.github.io/charts/)

My guess is that it would steamroller them, and assume the amazeeio.github.io domain for the userspace pages, not the organisation-space ones.

I'll have a dig through our documentation and try to make sure all the lagoon-cli links are properly update.

No idea what we can do about google search though. It's so annoying that GitHub doesn't cater for this!

[EDIT - I'll have to submit 80+ individual remove outdated content requests 😢]

@christopher-hopper
Copy link
Author

For my part, I've been fixing links in our Confluence and client Confluence pages, as well as README files in projects. I can only imagine that this is going to be a widespread and long-lived issue if a better solution is not available.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants