#11335 301 redirect for Silverblue
Closed: Fixed 11 months ago by ryanlerch. Opened 11 months ago by jamesbelchamber.

Describe what you would like us to do:


Put in place a 301 redirect from silverblue.fedoraproject.org to fedoraproject.org/silverblue to coincide with the launching of the new Silverblue website.

When do you need this to be done by? (YYYY/MM/DD)


As soon as reasonable - no fixed date really. I have proposed a PR for the old site here which, if merged, will perform a redirect that's equivalent to a 301 for most browsers and search engines.


Metadata Update from @ryanlerch:
- Issue assigned to ryanlerch

11 months ago

Metadata Update from @zlopez:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: low-trouble, medium-gain, ops

11 months ago

@ryanlerch i will take a look, it's simple redirection from apache config ?

@kevin do you agree ?

Yeah, although we also I guess need to remove the openshift-app from ansible (right now silverblue.fedoraproject.org is a small openshift app that generates the site and serves it)

Preferably, make the redirect a few days or so before removing the app.

It's not super important but.. you know, propagation.

On Wed, 24 May 2023, 17:54 Kevin Fenzi, pagure@pagure.io wrote:

kevin added a new comment to an issue you are following:
``
Yeah, although we also I guess need to remove the openshift-app from
ansible (right now silverblue.fedoraproject.org is a small openshift app
that generates the site and serves it)

``

To reply, visit the link below or just reply to this email
https://pagure.io/fedora-infrastructure/issue/11335

Metadata Update from @ryanlerch:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

11 months ago

Login to comment on this ticket.

Metadata
Boards 1
ops Status: Backlog