3 | | Changing a project master URL is not a trivial task. |
4 | | It's recommended that projects avoid keeping things prone to change in their project URLs, |
5 | | like using an IP address, |
6 | | or even putting the university they are in as part of the hostname |
7 | | (Docking@Home had to change the URL twice or so |
8 | | because they changed university / organization / department / something). |
9 | | Thus, the best way is having a domain name just for that project. |
| 3 | It's recommended that projects choose master URLs |
| 4 | that avoid anything prone to change, |
| 5 | especially in the hostname. |
| 6 | For example, even if you're still starting with a test project, |
| 7 | don't use an IP address in the URL; use an actual hostname. |
| 8 | Even having the university name as part of the hostname may be a bad idea. |
| 9 | In December 2007, |
| 10 | Docking@Home moved from the University of Texas at El Paso |
| 11 | to the University of Delaware, |
| 12 | and had to change their URL from docking.utep.edu to docking.cis.udel.edu. |
| 13 | Thus, the best way is having a hostname just for that project. |