On Tue, Sep 1, 2009 at 2:33 PM, Jorge G. Mare<koki@xxxxxxxxxxxxx> wrote: > For svn, why not just go directly with svn.haiku-os.org? Is it currently > being used? It wasn't - so I already updated the DNS in webfaction to point svn.haiku-os.org there (and Oliver tested this while I was chatting with him in IRC). > For the website and Trac, is it not possible to just create a test > subdomain for each of their respective VMs (ie., testweb.haiku-os.org > and testdev.haiku-os.org? Once those two installations are tested and > known to be running OK, then the DNS settings can be modified to point > to them. Or am I missing something? :) I think it would be OK to test everything with an alternate domain if it's convenient... as long as there are no hardcoded references to haiku-os.net anywhere ;) But we can also easily setup test subdomains as you suggest. >> Ah, I have no concerns about controlling the DNS myself - I simply didn't >> know that we as a group control the DNS already. I was assuming our current >> hoster would do so. >> > > It would still be convenient if those working on the new server had > access to the DNS settings; that way, you would not have to rely on > somebody across the ocean on a different time zone for a change that may > be required right away. Redundancy is this case is good IMO. ;) I agree, and I also think we should have someone in Europe with access to our Godaddy account in the event that emergency maintenance is needed. I would probably suggest Axel as he is currently on the Haiku, Inc. team anyhow. If we want to separate the duties further (for security reasons), and have DNS hosted outside of Godaddy for the domains that need to be maintained, I would be OK with that. Should we considering setting up DNS on our new server? or should we seek a good alternative DNS provider? Hopefully the changes to DNS are somewhat rare... - Urias