Decommission docs.bisq.network in favor of bisq.wiki

[cbeams]

From private Keybase chat on Jun 14:

@m52go wrote:

now that v1.6.5 has been out for a while, i think we can shut down docs.bisq.network.
is this something you can do in netlify? i assume it should just be a matter of flipping a switch in their interface.
it might also be good to redirect all requests to the docs subdomain to the wiki (docs.bisq.network/* --> bisq.wiki)

@cbeams wrote:

Will do. Will just do the redirect for now (via Cloudflare) and will shut off Netlify later. It doesn’t cost us anything, no harm in leaving it up.

@m52go wrote:

sounds good. i think the only other factor to consider is that the search engines may continue to index and show docs.bisq.network results (especially google) as long as the site is online, which can be problematic because there's some outdated information on there. but i guess with a redirect in place anyway it may not matter too much.

@cbeams wrote:

correct. with the redirect in place, search engines will no longer be able to index the content (formerly) at docs.bisq.network. The content will remain available at bisq-network-docs.netlify.com, but that url is not referenced anywhere.

[cbeams]

This change has been made and I am closing this issue as complete.

Before the change

$ curl -I https://docs.bisq.network
HTTP/2 200
[...]
server: Netlify

$ curl -I http://docs.bisq.network
HTTP/1.1 301 Moved Permanently
[...]
location: https://docs.bisq.network/
server: Netlify

After the change

$ curl -I https://docs.bisq.network
HTTP/2 301
[...]
location: https://bisq.wiki
server: cloudflare

$ curl -I http://docs.bisq.network
HTTP/1.1 301 Moved Permanently
[...]
Location: https://bisq.wiki
Server: cloudflare

Notes on changes to Cloudflare and DNS

This change involved setting up the following page rule at Cloudflare:

And to make the page rule take effect, it was necessary to start proxying DNS for docs.bisq.network through Cloudflare. Previously, DNS was un-proxied.

Notes on using a 301 redirect

I've opted to use a 301 (Permanent) redirect vs. a 302 (Temporary) redirect here, as my understanding is that 301s are better for search engine optimization, i.e. transferring ranking juice from docs.bisq.network to bisq.wiki. The potential downside of this approach is that if we were to bring docs.bisq.network back up, clients who had already received the 301 would keep the redirect cached and would not see that docs.bisq.network is actually back up and serving its content. This scenario seems unlikely, though, so just mentioning it here for completeness.

[cbeams]

I have also archived this repository and updated its description to reflect this change

If there are any issues, please bring them up in the Keybase #wiki channel.