I have accounts for several systems and I always have problems keeping my home environment up to date. I’ll create a script on one place and end up wanting to use it several more places. I’ll find a line to add to my .bashrc and end up missing it when I log into another system.
This was originally posted on Chris Heiland’s staff blog while he was a member of the Web Team. Chris migrated this post to the Web Team blog before he left because we thought the content still had value to the UW community. In Part 1 it was all about the WP Importer class, now that… Read More
Moving content from one system to another is always a conversation, many times it makes sense to rewrite and think about each new article. The goal should always be cleanup and enhance the experience for the user. However, in some cases it makes sense just to automatically script the process for expediency or when content doesn’t need to be modified.
A long time ago there was Common Gateway Interface (CGI), people used it because there was nothing better available. If you wanted your programming language on the web to generate HTML, there was no other option. The benefit was you could really use any language your server could support which ranged from popular such as perl, to the outright wacky bash.
Scavenger Hunt is an application that utilizes several technologies to make everything work seamlessly. The actual site runs off the main HuskyFest site that is built on WordPress.
I’ve finally gotten around to solving an interesting problem. For security purposes our primary webserver is read-only which makes some normally trivial tasks extremely difficult. Originally the system was design to push static files to the front end cluster so the web server could deliver.
I’m excited to announce I’ll be presenting at HighEdWeb this year in Austin, TX. I’ll have more information as the event nears but for now I’ll post the link to the talk. If you haven’t heard of this conference before, look it up. The content is diverse, the people are friendly and the presentations always helpful.
We had a problem where we needed two different varnish configuration files between our staging and production plone environments. Generating two files that do similar things is just too much work and unnecessary. However, there is a solution.
Finally, the CMS is migrated to the latest version of Plone and on to new hardware. The actual transition happened two weeks ago Friday but it’s been several days of testing. Anyone visiting the site should notice a huge speed improvement and a generally large increase in reliability.
This was originally posted on Chris Heiland’s staff blog while he was a member of the Web Team. Chris migrated this post to the Web Team blog before he left because we thought the content still had value to the UW community. I can’t imagine why this would ever be useful but I wanted to… Read More