Did you add an instruction to send an email to all users to tell them of
the URL change? The notices that a project is not working because of a URL
problem are buried in the message log, and disappear fairly quickly.
jm7
Nicolás Alvarez
<nicolas.alvarez@
gmail.com> To
Sent by: BOINC dev
<boinc_dev-bounce <[email protected]>
[email protected] cc
u>
Subject
Re: [boinc_dev] Changing master url
10/12/2009 05:51
PM
El Lunes 12 Oct 2009 14:08:54 Lynn W. Taylor escribió:
> Yes, I did.
>
> My comments are less about the process (which you covered very well) and
> more about prevention.
>
> If someone plans ahead, there is no reason for them to ever need to
> change the project URL.
That's what the first paragraphs, and the first step, are about :) But they
probably need expanding.
> I didn't see where you addressed functions inside a project -- apologies
> if I missed that.
I didn't. In the entire page, I assume the standard URL layout:
example.com/project/
example.com/project_cgi/cgi
example.com/project_cgi/file_upload_handler
My statement about multiple projects in one hostname is from past
experience
too. y...@home used to be in www.rechenkraft.net/yoyo, but then they had to
move the BOINC project out of the server hosting the Rechenkraft website,
changing the URL to boinc.rechenkraft.net/yoyo.
Your idea to have different hostnames per function is a good one.
If we do a better URL naming guide, I'd add a pet peeve: don't use
boinc.whatever.com! It sucks for browser history. You type "boinc." in the
address bar and dozens of projects show up. And BOINC main website. While
if
you type 'pri' you probably get Primegrid immediately.
> Your information is needed, because no matter how hard one tries, there
> will always be those who picked a URL, and didn't plan ahead.
The reason I wrote those instructions is that I have seen multiple times
that
admins change the URL thinking it's trivial, and then they can't contact
the
scheduler, workunits fail when downloading the app, etc. because they don't
realize how many places still have the old URL.
It mostly happens with non-public projects, though. People who use
http://localhost/test/ as master URL in the first attempt, and then they
want
to try with a second machine on their LAN...
--
Nicolas
_______________________________________________
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.
_______________________________________________
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.
