Decommission docs.bisq.network in favor of bisq.wiki about bisq-docs HOT 2 CLOSED

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.

from bisq-docs.

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.

from bisq-docs.