So... what about all those volunteers attached to the old project URL? With results, from the old URL, ready to be returned to the project? They will be trying to hit the old upload server, and scheduler.
Running Microsoft's "System Idle Process" will never help cure cancer, AIDS nor Alzheimer's. But running rose...@home just might! http://boinc.bakerlab.org/rosetta/ > Date: Sat, 10 Oct 2009 22:12:54 -0300 > From: Nicol?s Alvarez <[email protected]> > Subject: Re: [boinc_dev] Changing master url > To: [email protected] > Message-ID: <[email protected]> > Content-Type: text/plain; charset="iso-8859-1" > > El Jue 11 Jun 2009 14:40:27 Nicol?s Alvarez escribi?: > > El Jue 11 Jun 2009 14:15:21 Jeremy Cowles escribi?: > > > I created a project with an internal IP address > (192.x.x.x) and now I > > > want to test it with clients out on the internet. > So I've changed the > > > address to my public address (78.x.x.x) in > project.xml and recreated the > > > apps (xadd, update versions). > > > Now clients can attach to the project using the > public address, but they > > > fail to receive workunits. When I turn on more > detailed logging on the > > > client, I continue to see the 192.x.x.x address, > even though it says that > > > the main URL is 78.x.x.x (on the client). > > > > > > Is there something I need to do to reset the > client or the project? I > > > cant find instances of 192.x.x.x in any of the > configuration. > > > > Changing a project master URL is not a trivial task. > It's recommended that > > projects avoid keeping things prone to change in their > project URLs, like > > using an IP address, or even putting the university > they are in as part of > > the hostname (dock...@home had to change the URL twice > or so because they > > changed university / organization / department / > something). Thus, the best > > way is having a domain name just for that project. > Good URLs don't change. > > > > Even having multiple projects as > boinc.example.org/project1 and > > boinc.example.org/project2 may be problematic if you > eventually decide you > > want to move project2 to a different server. It's best > to have > > project1.example.org and project2.example.org so they > can (now or in the > > future) have different IP addresses. > > > > All that said, here is how you change a project URL: > > > > [...] > > > > [to be cleaned up and posted on the wiki] > > I *finally* got round to putting these instructions on the > wiki. > http://boinc.berkeley.edu/trac/wiki/ChangingMasterUrl > > David: I'll leave it to you to add a link to this new page > in an appropriate > place. > > -- > Nicolas > ...crossing off item in to-do list. > > > ------------------------------ > > _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
