As described in the server roles section, there are two webservers for the Museum's Research websites: a "live'', or publicly-available one, and a staging webserver, for prototyping changes to the sites. After changes have been made, viewed, and approved of, the new or altered files must be replicated to the live server and made public. This is what the webcp program is for.
webcp is run from a command line on the staging server. Only users with the privilege of publishing their site are able to run it, and they are able to publish select directories that are under their control. (You do not have to worry about someone else publishing your prototype content to the world.) Sometimes webcp ability is limited to a designated site maintainer, or a senior department member. For information on gaining publishing privileges, please see the section on getting an account.
Invoke webcp with the following syntax:
shell-prompt$ webcp <directory to publish>or
shell-prompt$ webcp <file to publish>In this example, <directory to publish> would be a web directory on the server's filesystem, like /srv/www/research/docs. Once you run webcp, you will need to wait until the replication finishes. For large directories where a lot has changed, this could take several minutes.
Here is an example:
shell-prompt$ webcp /srv/www/research/docs/my/site/... would take files in the staging website http://research-staging.amnh.org/my/site/ and publish them to the live server at http://research.amnh.org/my/site/.
You can also specify a file name instead of a directory. If you only need to publish a single file, this may be a lot faster than publishing the entire directory in which it resides.
If you receive errors that say, "permission denied'' or "send_files failed to open,'' the cause is probably that the directory you wish to copy is not world-readable, and you should investigate its filesystem permissions.
If you need a new research-related website and do not want it hosted on research.amnh.org, you may either use an alias on the amnh.org domain, or register a new domain for the site, and have that hosted on the Research webserver. An example of the former case would be newsite.amnh.org, and of the latter, www.newsite.org. Setting up a new hostname on amnh.org is easier and faster.
research.amnh.org is the live webserver for the Museum's Research-related sites. Any new Research department domain names or hostnames should be registered as aliases to research.amnh.org.
New domain names that are going to be hosted on Museum webservers should be registered with Network Systems as the administrative and technical contacts for the domain. Specifically, and at the very least, the technical contact email should be hostmaster@amnh.org. This makes it easier for them to be maintained.
We use ns-ext-1.amnh.org as the primary nameserver, and ns-ext-2.amnh.org as the secondary nameserver if you register a domain name (e.g. newsite.org). For example, in the information submitted to the registrar, these hostnames are used for the primary and secondary nameservers. Note that nothing needs to be registered with these organizations if there is just going to be a new host on the amnh.org domain, such as newsite.amnh.org.
Please contact us before you take any of the steps to arrange for a new domain or virtual host. The information above should let you know what to expect, but please contact us to let us help you put everything together.
Please contact us with web programming policy questions.