#8256 Redirect https://whatcanidoforfedora.org to http://asknot-asknot.apps.os.fedorainfracloud.org/en
Closed: Will Not/Can Not fix 3 years ago by cverna. Opened 3 years ago by cverna.

I have moved asknot-ng to communishift we need change the redirect to it http://asknot-asknot.apps.os.fedorainfracloud.org/en instead of our current OpenShift cluster.

Do we want to get https working on it first?

Metadata Update from @kevin:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: communishift

3 years ago

Can I work on this issue ?

Can I work on this issue ?

Sure! It's not a super easy one however... it's going to take a patch against our ansible repo in a bunch of proxy and other code. :(

I can try and give pointers if you are still interested...

@cverna to clarify here... you want us to keep pointing whatcanidoforfedora.org to our proxies and setup a redirect there that sends users to asknot-asknot.apps.os.fedorainfracloud.org ?

Or did you want to just add a route on communishift for whatcanidoforfedora.org and we can just change dns to directly go to it?

Oh I guess it is better to just create a https://whatcanidoforfedora.org route directly in communishift.

I ll do that then we can just change the dns :smile:

OK we now have a https://whatcanidoforfedora.org/ route in communishift.

Cool. Now we need to deal with the ssl cert. ;)

We could probibly do it with cert-manager (see ansible files/communishift/objects and look at the yml files for the api and apps certs) but we likely have to move the dns first?

Shoot, we would also need to setup some things in dns for that to work. cert-manager uses aws route-53 to validate, so we would have to setup the domain right for that.

Let's close that and keep asknot in OpenShift .

Metadata Update from @cverna:
- Issue close_status updated to: Will Not/Can Not fix
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.