[ElgertS]

Step 3: Create MySQL database

Using PHPMyAdmin, create a new database for PHPList. By default, it expects this to be “phplistdb”, but you can make it any name you prefer especially if you plan on running multiple copies of PHPList.

[ElgertS]

Step 2: Install PHPList on server

Open the resulting folder and navigate within the public_html folder. Copy the “lists” folder to your web hosting directory. If you want to have a site that is just for running PHPList, make this folder your site home, otherwise, place it within an existing website directory to act as a subfolder of that directory.

[ElgertS]

Step 1: Download PHPList

Download PHPList from the following URL:

PHPList 2.10.2

[ElgertS]

In case anyone else wants to try this I just want to point out how fantastic this has been for me. I have redone my configuration even further with the software, now using six volumes on my server:

1. Main volume is a “Mirror” of two 40G drives
2. “Safety Clone” is a partition of 40G using Super Duper’s Safety Clone feature which “shares” important data file (websites, mysql data, config files, email). This is what I normally am booting from.
3. “Mirror Backup” is a direct backup up my Mirror volume
4. “Safety Backup” is a direct backup of the Safety Clone volume
5. “ASR Images” is a drive that stores ASR images for faster restore

Since Super Duper has worked faster than CCC for me in tests and the script to backup just changes files will also remove new files that were added to the target to get them back in sync I have been able to make major changes to my Safety Clone, receive unsatisfactory results and boot off the Safety Backup to get the machine back online instantly and serving. Then use Super Duper to revert the Safety Clone volume back to what it last was in about 8 minutes of copy time.

Combining this with a reliable tape backup strategy has made me feel very comfortable with my server.

[ElgertS]

My concern is that if I do too many config files if the config file is what destroys my setup I will be out of luck and not able to go back again.

I see your point in having the data on another volume and believe that is inevitably the direction I will eventually head as something like that is probably required for clustering I would expect, something I one day hope to investigate.

So far, this setup has been the bomb for me. I feel no fears in doing crazy tests on a live server.

[ElgertS]

Step 7: Administration

You now can log into the front end or the administration back end of your Mambo website. Continue with the additional steps to add very useful features to Joomla for use with Firefox on Mac OS X.

[ElgertS]

Step 6: Additional Web Setup Screens

The next screen asks you for a description of your site. This is followed by a screen that verifies information about your site and requests the email and password for the Administrator account.

[ElgertS]

Step 5: MySQL Configuration

The next page asks about your MySQL setup. For host name give it “localhost” then give it the MySQL user name, password, and database you configured for the website. There are additional options you can choose such as loading the help data which might be helpful for learning Joomla.

[ElgertS]

Step 4: Web Configuration

Now load up your new website url and you will see the installation page. Verify that there are no red warnings on the first page. Make changes as necessary within your php.ini file if you have incompatible settings.

A great way to manage your php.ini is through Webmin, which with the 1.32 release added support for managing the php.ini file.

[ElgertS]

Step 3: Set Ownership

Next, using the Terminal, change the owner of the Joomla! directory to www:

[code]sudo chown -R www
[/code]

Note: If you are running Joomla! on a hosted environment and not on a Mac server, you will need to check with your hosting provider on how to manage Joomla! permissions and file ownership.

[ElgertS]

Step 2: Create a database for Joomla

Using phpMyAdmin, create a new database for your website. If you install quite a bit of AMP based projects you may want to consider an effective naming convention. I suggest the following convention for database naming:

site_project

If you are making a website for “Pizza Town” using Joomla, this would leave you with:

pizzatown_joomla

This allows you to group databases by relationship in the alphabetical listing within phpMyAdmin.

Alternatively, you can download the MySQL GUI Tools for Mac OS X and use MySQL Administrator to create and manage your databases.

[ElgertS]

Step 1: Download Joomla!

First, download Joomla! from the following link:

Joomla 1.0.12

Decompress the archive and move the resulting folder to your website directory, renaming it to reflect your goals for the website.

[ElgertS]

I have not tried using the standard alias feature in 10.3.2 to see if it is working now. What I did was turn off the apache module for virtual hosts. I then make each site as example.com and then I go into the site conf file using pico and at as the second field:

ServerAlias http://www.example.com

Add more entries for each additional alias you need.

[ElgertS]

The Fedora project has been updated to 1.2. This release adds content versioning of assets, improved interface, and new features to the Java client software.

[ElgertS]

Step 11: Test zenTrack

You are now ready to use zenTrack!

When you email tickets you can do the following commands:

send email with “help” as subject to get list of commands

send “create” as subject to get a template to make a new ticket

send ticket number and options ie: #7:options it will give you options for that ticket

Additional information:

http://zendocs.zentrack.net/bin/view/Zentrack/IndexPage

[Author]

Posts