php icon

Key Wiki Features

Posted in , , Sat, 30 Jun 2007 17:11:00 GMT

I just installed MediaWiki at an organization to manage some information I was researching. The primary reasons I chose MediaWiki were (a) it's open source, (b) it has auto-TOC (table of contents), (c) it has auto-categorization and (d) I was familiar with it already. I ran into some rough spots during the Win2K3 R2 / IIS 6.0 installation getting PHP 5.2.3 and the php_mysql extension working but other than that the installation was pretty smooth. It seems that the php_mysql extension that comes with PHP 5.2.3 doesn't work and you need to get it from PHP 5.2.2. Also, rebooting after installing PHP from the MSI helps but that doesn't seem to be mentioned in the installer. The other issue is that IIS doesn't seem to come with rewrite capabilities so I tried a third-party rewrite filter before tabling that for now. It's hard to believe that IIS doesn't have rewrite capabilities.

Some "Enterprise Wiki" solutions include Confluence and SocialText but I don't have any experience with these.

Which wiki do you like for "enterprise" purposes and what features do you find to be key? Do any other wikis have auto-TOC?

del.icio.us:Key Wiki Features digg:Key Wiki Features reddit:Key Wiki Features spurl:Key Wiki Features wists:Key Wiki Features simpy:Key Wiki Features newsvine:Key Wiki Features blinklist:Key Wiki Features furl:Key Wiki Features fark:Key Wiki Features blogmarks:Key Wiki Features Y!:Key Wiki Features smarking:Key Wiki Features magnolia:Key Wiki Features segnalo:Key Wiki Features

6 comments

catalyst icon

Single Sign-On (SSO) with and without subdomains

Posted in , , Sun, 17 Jun 2007 01:06:00 GMT

If you are running a site without a subdomain, e.g. http://dev411.com and need to maintain cookie-based sessions across other server names with subdomains, e.g. blog.dev411.com and wiki.dev411.com, you will need to customize your session cookies.

To have your session cookie be used across multiple subdomains, set a wildcard domain which starts with a dot followed by the base domain name, e.g. ".dev411.com", which will make it qualify for all subdomains of dev411.com. This, however, will not work for http://dev411.com where there is no subdomain.

The have the same session used for http://dev411.com, set a second session cookie without domain. This way the domain-less cookie will be used for http://dev411.com and the wildcard domain cookie will be used for all subdomains.

Catalyst 5.7007 will only set one cookie per cookie name, however, this solution works best when you can set both cookies with the same name but different cookie domains. I put together a quick patch for Catalyst::Engine to allow multiple cookies when the cookie value is set to an arrayref.

del.icio.us:Single Sign-On (SSO) with and without subdomains digg:Single Sign-On (SSO) with and without subdomains reddit:Single Sign-On (SSO) with and without subdomains spurl:Single Sign-On (SSO) with and without subdomains wists:Single Sign-On (SSO) with and without subdomains simpy:Single Sign-On (SSO) with and without subdomains newsvine:Single Sign-On (SSO) with and without subdomains blinklist:Single Sign-On (SSO) with and without subdomains furl:Single Sign-On (SSO) with and without subdomains fark:Single Sign-On (SSO) with and without subdomains blogmarks:Single Sign-On (SSO) with and without subdomains Y!:Single Sign-On (SSO) with and without subdomains smarking:Single Sign-On (SSO) with and without subdomains magnolia:Single Sign-On (SSO) with and without subdomains segnalo:Single Sign-On (SSO) with and without subdomains

1 comment

rails icontypo icon

Typo - Upgrading to 4.1.1

Posted in , Sat, 16 Jun 2007 22:36:00 GMT

I finally got around to upgrading from Typo 4.0.0 r1188 to Typo 4.1.1 and it was pretty smooth. I had held off for a while because Typo was changing a lot under the covers with some much needed refactoring and I have a few hacks I didn't feel like modifying with every minor update.

Read more...
del.icio.us:Typo - Upgrading to 4.1.1 digg:Typo - Upgrading to 4.1.1 reddit:Typo - Upgrading to 4.1.1 spurl:Typo - Upgrading to 4.1.1 wists:Typo - Upgrading to 4.1.1 simpy:Typo - Upgrading to 4.1.1 newsvine:Typo - Upgrading to 4.1.1 blinklist:Typo - Upgrading to 4.1.1 furl:Typo - Upgrading to 4.1.1 fark:Typo - Upgrading to 4.1.1 blogmarks:Typo - Upgrading to 4.1.1 Y!:Typo - Upgrading to 4.1.1 smarking:Typo - Upgrading to 4.1.1 magnolia:Typo - Upgrading to 4.1.1 segnalo:Typo - Upgrading to 4.1.1

no comments

typo icon

Displaying Dates and Times Using JavaScript

Posted in , , , , Tue, 06 Feb 2007 00:28:00 GMT

Some considerations when displaying dates and times on a website include showing delta times, customized timezones and caching. Often it's nice to show a delta time like "10 minutes ago" or "5 days ago" to give readers a frame of reference instead of an absolute date. When the date is far enough in the past and an absolute date becomes desired, customizing the date to the user's timezone is useful. And if your site grows large enough that caching becomes useful, finding a way to display customized deltas and timezone information in a cacheable static page becomes an ideal solution.

Read more...
del.icio.us:Displaying Dates and Times Using JavaScript digg:Displaying Dates and Times Using JavaScript reddit:Displaying Dates and Times Using JavaScript spurl:Displaying Dates and Times Using JavaScript wists:Displaying Dates and Times Using JavaScript simpy:Displaying Dates and Times Using JavaScript newsvine:Displaying Dates and Times Using JavaScript blinklist:Displaying Dates and Times Using JavaScript furl:Displaying Dates and Times Using JavaScript fark:Displaying Dates and Times Using JavaScript blogmarks:Displaying Dates and Times Using JavaScript Y!:Displaying Dates and Times Using JavaScript smarking:Displaying Dates and Times Using JavaScript magnolia:Displaying Dates and Times Using JavaScript segnalo:Displaying Dates and Times Using JavaScript

2 comments

Planning Ahead for Open Source Storage Scaling

Posted in Tue, 24 Oct 2006 16:56:00 GMT

Recently eWeek ran an article on eHarmony's storage scaling solution choice which discussed how they chose to go with proprietary solutions from 3PAR and ONStor. I was hoping to learn something interesting about their deployment architecture but the most interesting things I learned was that eHarmony has 8+ million users, 9+ million photos and their proprietary solution vendor choice. Some interesting quotes from Mark Douglas, eHarmony's VP of Technology:

Read more...
del.icio.us:Planning Ahead for Open Source Storage Scaling digg:Planning Ahead for Open Source Storage Scaling reddit:Planning Ahead for Open Source Storage Scaling spurl:Planning Ahead for Open Source Storage Scaling wists:Planning Ahead for Open Source Storage Scaling simpy:Planning Ahead for Open Source Storage Scaling newsvine:Planning Ahead for Open Source Storage Scaling blinklist:Planning Ahead for Open Source Storage Scaling furl:Planning Ahead for Open Source Storage Scaling fark:Planning Ahead for Open Source Storage Scaling blogmarks:Planning Ahead for Open Source Storage Scaling Y!:Planning Ahead for Open Source Storage Scaling smarking:Planning Ahead for Open Source Storage Scaling magnolia:Planning Ahead for Open Source Storage Scaling segnalo:Planning Ahead for Open Source Storage Scaling

no comments

apple icon

iPod, iTunes and DRM

Posted in Thu, 19 Oct 2006 04:03:00 GMT

I've been a happy iPod user for some time now, however I've only ever used my single iPod with a single iTunes install. I recently reinstalled my OS after wiping the hard drive for a clean start. To my surprise a fresh install of iTunes with the same iPod serial number would not import songs from my iPod into the iTunes library. iTunes had the gall to ask me if I wanted it to erase all the music on my iPod and replace it with the (empty) contents in its library. Essentially my iPod was orphaned. I've never thought about Apple DRM issues before but I'm no longer as excited about the iPod and iTunes as I was before.

Read more...
del.icio.us:iPod, iTunes and DRM digg:iPod, iTunes and DRM reddit:iPod, iTunes and DRM spurl:iPod, iTunes and DRM wists:iPod, iTunes and DRM simpy:iPod, iTunes and DRM newsvine:iPod, iTunes and DRM blinklist:iPod, iTunes and DRM furl:iPod, iTunes and DRM fark:iPod, iTunes and DRM blogmarks:iPod, iTunes and DRM Y!:iPod, iTunes and DRM smarking:iPod, iTunes and DRM magnolia:iPod, iTunes and DRM segnalo:iPod, iTunes and DRM

6 comments

mysql icon

MySQL Deployment Presentations

Posted in , Fri, 06 Oct 2006 03:07:00 GMT

I just ran across the MySQL Web 2.0 page which lists a number of their users including the following:

MySQL Web2.0

The most interesting thing from that page, however, is links to various presentations given by those sites on how they architected their sites to scale with MySQL, some of them scaling up to hundreds of MySQL servers.

Read more...
del.icio.us:MySQL Deployment Presentations digg:MySQL Deployment Presentations reddit:MySQL Deployment Presentations spurl:MySQL Deployment Presentations wists:MySQL Deployment Presentations simpy:MySQL Deployment Presentations newsvine:MySQL Deployment Presentations blinklist:MySQL Deployment Presentations furl:MySQL Deployment Presentations fark:MySQL Deployment Presentations blogmarks:MySQL Deployment Presentations Y!:MySQL Deployment Presentations smarking:MySQL Deployment Presentations magnolia:MySQL Deployment Presentations segnalo:MySQL Deployment Presentations

2 comments

mysql iconperl iconunicode icon

Perl, MySQL and UTF-8

Posted in , , , Mon, 02 Oct 2006 15:35:00 GMT

One of the mysteries of Perl to me is that why, as of yet, is there no UTF-8 support in DBD::mysql although this issue has been discussed on the msql-mysql-modules list since at least 2003 (using the MARC archives). This is also given that MySQL does have UTF-8 support itself.

Read more...
del.icio.us:Perl, MySQL and UTF-8 digg:Perl, MySQL and UTF-8 reddit:Perl, MySQL and UTF-8 spurl:Perl, MySQL and UTF-8 wists:Perl, MySQL and UTF-8 simpy:Perl, MySQL and UTF-8 newsvine:Perl, MySQL and UTF-8 blinklist:Perl, MySQL and UTF-8 furl:Perl, MySQL and UTF-8 fark:Perl, MySQL and UTF-8 blogmarks:Perl, MySQL and UTF-8 Y!:Perl, MySQL and UTF-8 smarking:Perl, MySQL and UTF-8 magnolia:Perl, MySQL and UTF-8 segnalo:Perl, MySQL and UTF-8

8 comments

mysql iconperl iconxapian icon

Encoding Hashed UIDs: Base64 vs. Hex vs. Base32

Posted in , , Mon, 02 Oct 2006 08:08:00 GMT

I recently looked at using various encodings for hashed UIDs, e.g. UIDs generated by a crytographic hash algorithm such as SHA-1 or MD5. These are often useful when the UID does not need to have human meaning but should exhibit some uniformity, such as character set and length. I considered Base64 and hexadecimal first because they are commonly used by crypto libraries and then decided on Base64 and Base32 where appropriate. Base36 is actually the most compact case insensitive encoding (using Arabic numbers and Roman letters) but is not an option for me at the moment because there's no Perl module for it that will take arbitrary text and binary input at the moment. Math::Base36 exists but only handles numbers.

Read more...
del.icio.us:Encoding Hashed UIDs: Base64 vs. Hex vs. Base32 digg:Encoding Hashed UIDs: Base64 vs. Hex vs. Base32 reddit:Encoding Hashed UIDs: Base64 vs. Hex vs. Base32 spurl:Encoding Hashed UIDs: Base64 vs. Hex vs. Base32 wists:Encoding Hashed UIDs: Base64 vs. Hex vs. Base32 simpy:Encoding Hashed UIDs: Base64 vs. Hex vs. Base32 newsvine:Encoding Hashed UIDs: Base64 vs. Hex vs. Base32 blinklist:Encoding Hashed UIDs: Base64 vs. Hex vs. Base32 furl:Encoding Hashed UIDs: Base64 vs. Hex vs. Base32 fark:Encoding Hashed UIDs: Base64 vs. Hex vs. Base32 blogmarks:Encoding Hashed UIDs: Base64 vs. Hex vs. Base32 Y!:Encoding Hashed UIDs: Base64 vs. Hex vs. Base32 smarking:Encoding Hashed UIDs: Base64 vs. Hex vs. Base32 magnolia:Encoding Hashed UIDs: Base64 vs. Hex vs. Base32 segnalo:Encoding Hashed UIDs: Base64 vs. Hex vs. Base32

no comments

perl iconunicode iconpostgresql icon

Perl - Strictify utf8 to UTF-8

Posted in , , Fri, 29 Sep 2006 18:21:00 GMT

Perl has two UTF-8 encodings, utf8 which is Perl's liberal version and UTF-8 which is a strict interpretation, aka utf-8-strict. The liberal version allows for encoded characters outside the UTF-8 character set, however you can run into problems when interoperating with applications that expect utf-8-strict, such as PostgreSQL. Here's a function I wrote to strictify utf8 to UTF-8 using the Encode core module:

use Encode;

sub strictify_utf8 {
    my $data = shift;
    if (Encode::is_utf8($data) && !Encode::is_utf8($data,1)) {
        Encode::_utf8_off($data);
        Encode::from_to($data, 'utf8', 'UTF-8');
        Encode::_utf8_on($data);
    }
    return $data;
}
del.icio.us:Perl - Strictify utf8 to UTF-8 digg:Perl - Strictify utf8 to UTF-8 reddit:Perl - Strictify utf8 to UTF-8 spurl:Perl - Strictify utf8 to UTF-8 wists:Perl - Strictify utf8 to UTF-8 simpy:Perl - Strictify utf8 to UTF-8 newsvine:Perl - Strictify utf8 to UTF-8 blinklist:Perl - Strictify utf8 to UTF-8 furl:Perl - Strictify utf8 to UTF-8 fark:Perl - Strictify utf8 to UTF-8 blogmarks:Perl - Strictify utf8 to UTF-8 Y!:Perl - Strictify utf8 to UTF-8 smarking:Perl - Strictify utf8 to UTF-8 magnolia:Perl - Strictify utf8 to UTF-8 segnalo:Perl - Strictify utf8 to UTF-8

no comments

Older posts: 1 2 3 4 5 ... 10