|
|
 |
Using PostNuke
|
 |
 |
|
 |
 |
The experience of working with PostNuke for the first time has been a largely positive one. The knowledge required to implement a generic PostNuke install is nothing more than the experience necessary to implement Gallery or PHPBB and a plethora of configuration options are nicely tied together by the admin interface, with direct dabbling in config files being completely unnecessary for most purposes. Getting the most out of it in the long run and fully configuring a template to work well with a specific set of desired functions would seem to require some dabbling in PHP or at least cutting and pasting of relevant snippets of code, but the basic install and module configuration is simple as can be.
PostNuke installation is essentially a process accessible to anyone who's familiar with generic end-user web apps (specifically, any web browser and any FTP app), which is to say, it is perfectly accessible to the majority of Canadian teenagers in the present day 'out of the box' as it were (or in this case, out of the tar.gz). The only element of the install which might be foreign territory to new users of general audience PHP apps is the matter of making necessary file and directory permissions changes before and after install. But that's easily enough explained in any tutorial, and is a process identical to that undergone during installation of any similar app (i.e., make the config.php writable, make it read only, delete the install files).
Postnuke contributors have hacked the aforementioned major PHP projects into the Postnuke module system, so it looks like throwing a PN-customised PHPBB or image gallery into the mix is even easier than it would be were it to consist of a separate PHPBB or Gallery installation. PN may turn out to be, even independent of its own virtues, a great way to tie together these projects under a single user login.
|
 |
 |
|
 |
 |
|
|
|
|
|
|
![Welcome to ASKimberley's [FIS]Blog](themes/Icey/images/logo.gif){kind=logo}
