www.cs.miami.edu/~[username] is now supplemented with www.cs.miami.edu/home/[username].
This change allows [username]‘s homepages to be addressed by both style URL’s.
Your account was created with a symbolic self-link “public_html->.” in you public_html directory. This self-link means that the new URL scheme will work along side the old URL scheme without any change to your homepages.
If one or the other URL is not working, it is easy enough to fix.
WordPress for the department is moving to a new computer. Using the new “Network Admin” possibilities of WordPress 3.0. It is a big improvement.
Some tricks for wordpress users:
To move a site, it helps to change the url’s in the database:
mysql> update wp_options set option_value='http://jackson.cs.miami.edu/burt' where option_name='siteurl';
Query OK, 1 row affected (0.00 sec)
Rows matched: 1 Changed: 1 Warnings: 0
mysql> update wp_options set option_value='http://jackson.cs.miami.edu/burt' where option_name='home';
Query OK, 1 row affected (0.00 sec)
Rows matched: 1 Changed: 1 Warnings: 0
If you don’t do this, you get some pages to work, but then it will jump to the URL as described by these values. This worked pretty good on the old WordPress, and might work on WordPress 3.0 without Network Admin enabled. I couldn’t migrate the URL of a 3.0 with Network Admin and ended up dropping the entire database and starting again.
In general, it is hard to change the URL of a wordpress site. When migrating a site there just has to be downtime – export the data and shut down the old site; fix the DNS and install at the new machine on the desired URL.
To set the password, find a working user_pass from another blog, with known password:
mysql> update wp_users set user_pass='$P$BV3q/rYU98poi/Zv/ARuStuPi.Wvad.' where user_login='admin';
Query OK, 1 row affected (0.02 sec)
Rows matched: 1 Changed: 1 Warnings: 0
The subversion server has been moved to a new machine. The CNAME svn.cs.miami.edu will lead you to it. It’s actual name is meade-vma.
Changed is the network service style. Previously the repositories were accessed using webDAV and Apache, and the repository URL used http:// as the prefix.
Now svnserve is being used, and the URL should be svn://svn.cs.miami.edu/[path-name].
Route 53 went live as of June 26. There are now two infrastructures for the department’s DNS servers for forward resolution (that is, from name to IP address). We maintain the classic BIND named’s, housed in the department with on-campus secondaries to cover short term outage and maintenance; and a parallel cloud DNS service that can withstand wide spread catastrophe.
We are testing using Route53, a cloud-provisioned DNS service from Amazon, for a secondary DNS system.
The Ungar building suffered a power outage. Our web servers were out for an hour or so, to avoid overheating. Sorry. Back now.
Ssh has a thing called DynamicForward. It is actually SOCKSv5. Since Firefox is socks enabled, you can use your cs account as a proxy for web browsing. This is useful, for instance, to get to web pages that are only available from inside UM, such as CCS, or some of our internal-only sites.
What happens is that all HTTP requests are sent to port 1080 on your localhost, wrapped inside of a SOCK protocol. That request goes into the ssh session and emerges on whatever machine you are ssh-ing to, say Lee. Lee makes the HTTP request in proxy for your browser, and returns the response back through the ssh channel.
Subversion server going on line at svn.cs.miami.edu. An experiment with use in class at the unofficial name web.cs.miami.edu/svn/repos. Authentication is an unsettled issue.
The wiki needs to be reinstalled, and the visual aspect redone. In the meanwhile, the wildpages will point here.