I started editing the DNS records. Some can’t be edited (autoconfig, *.jabber, www.*, ssh, ssh.*), so I guess they are automatically provided by dreamhost. Some of those appear to be created because things like wiki.octave.org were set up as separate subdomains for hosting purposes so when those are converted to A records, the corresponding www.wiki and ssh.wiki DNS records will go away.
The one significant change I’ve made so far is to change wiki.octave.org from a subdomain hosted at dreamhost to an A record (18.104.22.168, the fosshost site). I’m now seeing the new DNS record and connecting appears to work. I saw a certificate error when I first connected, but I assume that is temporary.
Is there some reason to prefer using A records for the bugs, docs, hg, wiki, etc. subdomains instead of using CNAME records that point to a single A record for fosshost.octave.org?
We don’t allow write access to the hg archives with https. You have to use ssh. I think Jordi set it up. It appears to have all the archives under a single user ID and access is controlled with the hg-ssh script and using a command= option in the shared user’s ~/.ssh/authorized_keys file. If there is a better way, now would be a good time to switch, so I’d say set it up in whatever way is best.
Yes, there is a cron job running every 10 minutes that executes a script to update hg.octave.org/octave from http://hg.savannah.gnu.org/hgweb/octave. Brute force, but I guess it usually works. Again, if there is a better way, we can do whatever is needed.
Yes, this should be resolved now if you close and reopen your browser.
To my humble knowledge, CNAMEs can only refer to subdomains of the same IP address. As we are currently stuck between two servers with different IP addresses, I thought this is the safest option and does not really hurt in praxis. But feel free to convert subdomains of the same IP address to CNAME records. Please edit my first post accordingly.
I made bugs.octave.org, docs.octave.org, and wiki.octave.org CNAME records pointing to fosshost.octave.org. The fosshost.octave.org name is still an A record. This way, if we move the entire collection of services to some new place or the IP address of our machine on FossHost changes, we only have to update the one A record.
Let me know when you are ready for any other DNS changes.
I’m also uploading the script used on the current hg.octave.org to mirror the Octave sources from savannah. It looks like we used to have the Mercurial archives on Dreamhost and some parts of the script might not be needed now.
I’m getting a problem accessing bugs.octave.org: it either redirects to wiki.octave.org or it gives me a warning about a security certificate which is not valid for bugs.octave.org:
Websites prove their identity via certificates. Firefox does not trust this site because it uses a certificate that is not valid for bugs.octave.org. The certificate is only valid for the following names: fosshost.octave.org, hg.octave.space, wiki.octave.org
Error code: SSL_ERROR_BAD_CERT_DOMAIN
How to trigger: Visit this page: Bugs and click the link at the top that says “browse recent bugs”.
I’d like to move the buildbot server to fosshost. I can help with that configuration. hg.octave.org is also moving to fosshost. Once those things are done, agora.octave.org can be deleted and I’ll probably close my Digital Ocean account since I don’t have anything else hosted there.
What is needed to move packages.octave.org to fosshost? On dreamhost, it is just a couple of small .htaccess files. Once it is moved, I’ll delete the subdomain and make packages.octave.org a CNAME for fosshost.octave.org.
Some of the buildbot workers run on my personal systems but the buildbot master server (the part of buildbot that provides the web interface and scheduler) runs on a Digital Ocean system (primary name is agora.octave.org). The only thing I want to move to the fosshost server is what is running on the Digital Ocean system. The workers will remain as they are now.