Of course there are variations on that opinion. But that is neither here nor there. The purpose of this tutorial is to help you get a PostgreSQL server up and running quickly and easily. To make this simple we will make this a part of our Ubuntu Server series, so all you have to do is have your Ubuntu Server up and running (see my article “Installing Ubuntu Server 9.04” to get started.) Once you have that server up and running you are ready to get your PostgreSQL server up.

Installation

The first thing you need to do is to install the necessary software. Since this is Ubuntu, it’s quite easy. Open up a terminal window and issue the command:

sudo apt-get install postgresql

Once the software is installed you are ready to set it all up.

Change the default user password

One of the first steps you want to take is to change the default password for the user postgres. Sine we are using Ubuntu you will have to use the sudo command to change to the postgres user like so:

sudo su – postgres

You will have to enter your sudo password after which you will now be issuing commands as the user postgres. The next step is to gain access to the postgresql command prompt with the command:

psql

Your new command prompt will look like:

postgres=#

NOTE: The only user that can open the PostgreSQL prompt without defining a database to work with is the user postgres. Other users would have to gain access to the command prompt with a command like:

psql DB_NAME

Where DB_NAME is the name of an existing database.

Changing the password is as simple as issuing the command:

\password postgres

You will then be asked to enter a password and then verify that password.

Your default password has not been changed. You can exit from the PostgreSQL prompt by issuing the command:

\q

Create a database

Now, while still logged in as the postgres user, let’s create a database. For this you do not have to be logged into the PostgreSQL command prompt. Instead just issue the command:

createdb testdb

Where testdb is the name of the database you want to create. To check to make sure that database was created go back to the PostgreSQL command prompt (remember, the command psql) and enter:

\l

You should see a listing for your new database like:

testdb | postgres | UTF8 | en_US.UTF-8  | en_US.UTF-8

Once again, log out of the PostgreSQL command prompt with the command:

\q

Create a user

By default, the only user that can connect to a database is the postgres user. This will be of no help when you need to connect with another user. To create a new user (that can connect to databases) you would issue the command (as the user postgres):

createuser –superuser USERNAME

Where USERNAME is the name of the user you want to create.

Final thoughts

Now you should have a basic PostgreSQL installation with a test database and a user, besides postgres, that can work with the tools. Next time we work with PostgreSQL we’ll discuss more challenging issues with this outstanding database tool.

Related posts

• Set up MySQL database replication (1)
• Install phpmyadmin for easy MySQL administration (6)
• Have WordPress back-ups emailed (3)
• Database Monitoring Software Db2rss (1)
• Backup MySQL Databases In Linux Regularly (11)

Wampserver is an Apache web server for the Windows operating system. It provides in many regards the same functionality of other web server solutions like XAMPP or Home Web Server which we have reviewed in the past. The latest version of the local web server package will install Apache 2.2.11, MySQL 5.1.36 and PHP 5.3.0 on the local computer system.

One interesting unique feature is the ability to add different versions of Apache, MySQL and PHP to the installation in the form of add-ons. This can be very handy to test a website locally under multiple different Apache, MySQL or PHP release versions.

The installation of Wampserver will always install the latest versions of Apache, MySQL and PHP. One interesting security feature is the ability to limit access to the web server to localhost. It is required to click on the “put online” option to make it available to other computer systems as well.

Additional Apache, MySQL and PHP versions can be installed from the Wamp add-ons page. All add-ons are provided as executables that can be installed easily on the operating system.

Webmasters who need to test code offline can use Wampserver to do so. It is especially useful to test code against multiple versions of Apache, MySQL and PHP. Something that the other home server solutions do not provide.

Wampserver is Open Source and can be downloaded from the developer’s website.

Related posts

• Portable Web Server (8)
• How to: Install a LAMP server (7)
• Host your own webserver (18)
• Web Development: Standardizing variables to code faster (18)
• Web Development: PHP – what role does it fill (1)

We have dealt with several services in the past including the network monitoring software Open Monitor or the online service Livewatch.

The database monitoring software dv2rss is different from these solutions. The main difference is that it can – as the title implies – monitor databases but also because it can only be run from the command line or a script. That’s not as bad as it sounds and it could be welcome in certain situations where no graphical user interface is needed or wanted.

Db2rss supports MySQL, Interbase and Blackfish SQL databases at the moment and can monitor them in a computer network or on the Internet. It comes with several command line parameters that define important information such as the database’s host name, the username and password. There are quite a few additional parameter that include running an SQL command on the database, comparing the results to a local copy and defining templates and title of the resulting RSS feed. The RSS feed is another aspect of this database monitoring software that is usually not found in other monitoring software programs.

It is then possible to subscribe to the RSS feed to receive the database monitoring information after the script’s execution. The software developer suggests to use the Windows task scheduler to run the database monitoring software regularly.

Related posts

• Backup MySQL Databases In Linux Regularly (11)
• Set up MySQL database replication (1)
• Install phpmyadmin for easy MySQL administration (6)
• Have WordPress back-ups emailed (3)
• Basic postgresql server setup (5)

• Linux
• Apache
• MySQL
• P (can mean PHP or PERL – depends upon your needs)

LAMP servers are very popular, cheap, effective, flexible, and reliable servers. But how are they installed? Actually, it’s not that hard. In this tutorial I am going to show you how to install a LAMP in two different ways: From the command line (using separate tools) and using the tasksel tool.

Hardware needed

Fortunately a LAMP server can be installed on lower-end hardware and still serve as a fairly efficient server. Naturally if you are going to be using your LAMP server for high traffic, you will want to select your hardware wisely.

Install prerequisite

Before you begin the installation of your server you will need to have your operating system installed. This is the “L” of LAMP. So find your favorite Linux distribution and install the operating system. For the purposes of this installation I am going to be installing on a Ubuntu 9.04 server installation. This will be a console only server (no GUI desktop) which is fine because the installation is done via command line only.

Once you have your operating system installed you are ready to install your server.

Apache

This is the easiest portion to install. Either log in to your console or open up a terminal window (if you are working from a GUI desktop) and enter the following command:
sudo apt-get install apache2

You will have to enter your sudo user password for this installation to continue. Once this installation is complete check it by pointing a browser to that server IP address. You should instantly know if Apache is up and running.

PHP

For the purposes of this article we will assume the “P” stands for PHP. To install PHP (and all of its requirements) issue the command:

sudo apt-get install php5 libapache2-mod-php5

Once this installation is complete restart Apache with the command:

sudo /etc/init.d/apache2 restart

Let’s make sure this portion works properly. To test this create a file in the Apache document root (for this install it will be /var/www) called test.php. The contents of this file will be:
< ?php phpinfo(); ?>

Save that file and then point your browser to http://IP_ADDRESS/test.php

Where IP_ADDRESS is the actual IP address of your server.

You should see “Test PHP Page” written on your browsers page. If so, you’re good to go.

MySQL

Now to install MySQL. To do this issue the command:

sudo apt-get install mysql-server

Once this is done you then need to set a password for MySQL. To do this issue the command:

mysql -u root

which will put you in the MySQL prompt. From this prompt (which looks like mysql> ) enter the command:
SET PASSWORD FOR 'root'@'localhost' = PASSWORD('YOURPASSWORD');

Where YOURPASSWORD is the password you want to use for the mysql user.

Now start your MySQL server with the command:

/etc/init.d/mysql start

That’s it. Your LAMP server is up and running.

The quick version

You can actually install a full-on LAMP server on a (Ubuntu server install) with a single command:

sudo tasksel

You will need to select LAMP from the list and you will eventually be prompted for a MySQL password. That’s it.

Final thoughts

Getting a powerful, flexible web server up and running will take you less time and effort than you think. LAMP servers are an outstanding choice for your web servers’ needs.

Related posts

• Portable Web Server (8)
• PHP – what it does and what it doesn’t (4)
• Local Apache Web Server Wampserver (3)
• Web Development: Standardizing variables to code faster (18)
• Web Development: PHP – what role does it fill (1)

Many web hosting companies offer backup space and create backups regularly. Some on the other hand ask for additional payments or do not offer this backup service at all. It then is up to the webmaster or server administrator to ensure that the data gets backed up regularly so that it can be restored when needed.

One option that is becoming increasingly popular is to backup data and send it to an offsite storage space. Backup2Mail is such a script. It can initiate automatic MySQL database backups on Linux servers using cron jobs and transfer these backups to a Gmail account. The only restriction is that the size of the zipped database should not exceed the maximum attachment limit of Gmail which is currently 25 Megabytes.

The developer provides instructions on how to setup the MySQL database backup and Gmail transfer on his website. It basically means that the user needs to edit an index.php file to provide the script with the MySQL information and GMail data. The only thing left after this step is to create a cron job so that the script is executed regularly on the server. Backups will from then on be created automatically on the web server and send to the Gmail account.

Related posts

• Yahoo to offer unlimited Email Storage (8)
• Yahoo Mail, Search And Messenger Upgrades (2)
• Xoopit To Become Yahoo Mail Exclusive (5)
• Wiredtree Review After Four Months (3)
• Windows SSH Server WinSSHD (3)

Database replication will require the use of two machines. The reason you want to use two machines is to ensure you will always have a working copy of your database (should one machine die). When using replication you think of your machines as Master and Slave. The Master is the machine that holds the original database. The Slave is the machine that holds the replicated database (the backup per say.) Both machines must have a working MySQL installation and must be networked together. You will need root access as well as access to the database administrator on both machines.

Setting up the Master

For purpose of example our database to replicate will be called “sample_database”.? The first thing you need to do is open up the /etc/mysql/my.conf file for editing. You need to search for the lines:

#skip-networking
#bind-address = 127.0.0.1

Uncomment out these lines (remove the “#” character). If these lines do not exist, add them. Now we have to inform mysql which database we plan on replicating. For this you will add the following lines:
log-bin = /var/log/mysql/mysql-bin.log
binlog-do-db=sample_database
server-id=1

The above lines do the following:

Line 1: Instruct mysql what log file to use.

Line 2: Instruct mysql which database to replicate

Line 3: Instruct mysql that this machine is the master.

Restart mysql on this machine with the following command:

/etc/init.d/mysql restart

The next step is to log into the mysql terminal and create a user that has replication privileges. To do this issue the command:

mysql -u root -p

You will prompted for the mysql admin password. Now we have to make some mysql magic. From the mysql prompt issue the following:

GRANT REPLICATION SLAVE ON *.* TO 'USER'@'%' IDENTIFIED BY '';

Where NEW_PASSWORD is the actual password and USER is the actual username that will have replication privileges.

Now issue the command:

FLUSH PRIVILEGES;

You’re not done with mysql yet. Now issue the command:

USE sample_database;

And now the command:

FLUSH TABLES WITH READ LOCK;

And now you need to make sure mysql is seeing the Master and can show the status of the master with the command:

SHOW MASTER STATUS;

When you issue the above command you should see a listing printed out for your sample_database. Write this information down (you will see a Position number that you will need later).
Now you need to get tables and data from the sample_database. The method I will show you requires that the database on the Master be locked momentarily. To that end the database will be unavailable until the database is unlocked. Keep this in mind when setting this up.

Now you’re ready to set up the Slave. Move over to the machine that will serve as the slave.

The first thing to do on the Slave is to create the database the Master will write to. On the slave open up the mysql shell with:

mysql -u root -p

You will be prompted for the password. Now enter the following command to create the database:

CREATE DATABASE sample_database;

And quit mysql with the “quit” command.

Now to configure MySQL to know it is the slave and open up the /etc/mysql/my.conf file for editing. Add the following lines:
server-id=2
master-host=IP_ADDRESS_OF_MASTER
master-user=USER
master-password=USER_PASSWORD
master-connect-retry=60
replicate-do-db=sample_database

Where IP_ADDRESS_OF_MASTER is the actual IP address of the master server, USER is the user created on the master for replication, and USER_PASSWORD is the password given to the replication user on the Master.

Save that file and restart mysql on the slave with the command:

/etc/init.d/mysql restart

Now we have to load the data from the Master into the Slave. This is when the database will be locked. Here are the commands to load the data:

mysql -u root -p

Enter the mysql admin password. Now from the mysql prompt enter the following command:

LOAD DATA FROM MASTER;

Now exit the mysql prompt with the command quit.

The next step is to stop the slave so you can finish up the Slave configuration. Issue the following:

mysql -u root -p

You will prompted for the root password.

now enter the command:

SLAVE STOP;

Now the next command is a bit lengthy:

CHANGE MASTER TO MASTER_HOST='IP_ADDRESS_OF_MASTER', MASTER_USER='USER', MASTER_PASSWORD='USER_PASSWORD', MASTER_LOG_FILE='mysql-bin.007', MASTER_LOG_POS=NUMBER;

Where:
IP_ADDRESS_OF_MASTER is the actual IP address of the Master server.
USER is the actual user you created on the Master.
USER_PASSWORD is the actual password you gave the user on the Master.
mysql-bin.007 is the File name from the output of the SHOW MASTER STATUS command from above.
MASTER_LOG_POS is the Position given in the output of the SHOW MASTER STATUS command from above.

Finally issue the command:

SLAVE START;

and then quit the mysql prompt with the command “quit”.

You’re done. If you have phpmyadmin installed you can check the status of the databases as they updated. You now have database replication up and running. Congratulations.

Related posts

• Install phpmyadmin for easy MySQL administration (6)
• Backup MySQL Databases In Linux Regularly (11)
• Have WordPress back-ups emailed (3)
• Database Monitoring Software Db2rss (1)
• Basic postgresql server setup (5)

We had a look at how a mysql query basically works, which will come in handy if you’re just learning about MySQL and PHP. The article focuses more on the technical side than how to create specific queries, but we’ll get there in the end too! Just after that we created some simple but effective excerpts from longer text automatically removing unwanted characters and spaces.

We also had a look at website mascots, why you should use them, how to use arithmetic operators in PHP and just today, why a coder should always be well slept (easier said than done). If you feel like taking a stroll down web development avanue visit the site, or follow us on Twitter or our RSS feed!

Related posts

• Web Development: PHP – what role does it fill (1)
• PHP – what it does and what it doesn’t (4)
• Web Development: Standardizing variables to code faster (18)
• Scriptastique web development roundup (4)
• Portable Web Server (8)

The most common server architecture on which PHP is found is called LAMP (for Linux + Apache + MySQL + PHP). All of the elements of LAMP are open source, meaning that the source code of the application is freely available. This means that the cost of setting up a server running LAMP is reduced (No License Fees), so LAMP based web hosting tends to be the least expensive solution available.

The Internet is built on a client-server architecture. On the client side we have the user and the browser. One the server side we have the server and its script interpreter (In our case, Apache and PHP).
Because PHP runs on the server side, we cannot use it for flashy client side effects, things like animations and auto-complete cannot be performed by php because php is only running on the server. For client side programming we could use javascript, Flash/Flex, Silverlight, or JavaFX.

What we can do with PHP is access a database, connect to other websites/services for information, and build a page out of smaller pieces, which we then deliver to the client for rendering.

I think it is important to indicate at this time that there are four levels at which you can work with PHP.

1. Scripting – this is where you take a small script and add it (integrate) into an existing page.
2. Coding – this is where you write scripts as needed to add basic functionality to your site.
3. Development – this is where you write an full application in PHP.
4. Architect – this is where you properly design an application that develop it into an application. Like development but puts a lot more thought into a good foundation.

Depending on your actual needs, several of these layers could be overkill for your task. The following articles will mainly be focused on the first two levels – scripting, and coding. In Scripting and coding we have two primary tasks we accomplish. One makes your job as webmaster easier. The second adds new functionality to your site.

Jeremiah Stover is a Software Engineer and a Business IT Consultant at Pragmatic Development. He has hands on experience and regularly provides practical advice in Business, Marketing, IT equipment and software. His Specialties include interpersonal communications, design skills, teaching and instruction. Right now he spends most of his time developing web applications in PHP and MySQL.

Related posts

• Web Development: PHP – what role does it fill (1)
• Ghacks Web Development PDF Article Compilation January 09 (6)
• Web Development: HTML Playground (7)
• Web development roundup (1)
• Scriptastique web development roundup (4)

HTML is a markup language that lets us describe attributes of the text and blocks on our pages. This works great for simple requests, making pages much more interesting than plain text. However it leaves us with a very simple structure. One page from One url (address) results in one rendered content (every time this url is requested, the output is the same).

To give us more options we have programming languages. Some like PHP run on the server side. They modify the content that will be displayed before it is sent to the client and on to the browser. Others like JavaScript run on the client side and allow changes to be made in the browser after the page has been rendered – usually for interactivity or for adding a feature not normally available in that browser.

The very first thing you _must_ do before getting started with PHP is get a good grasp of HTML (and CSS). Many webmasters use a tool like Dreamweaver, Expression Web or KompoZer. To
work with PHP it is important that you understand the underlying HTML code. You will be modifying this code so you need to be able to understand the HTML well enough to understand what you see.

If you like video training try Lynda.com or VTC.com. If you prefer reading a book try “Head First html with CSS & Xhtml” or if you prefer free web instruction try w3schools.com and tizag.com.

Now that you understand the markup language which is what is sent to the browser (HTML) you are ready to tackle the server side use of PHP.

Jeremiah Stover is a Software Developer at Pragmatic Development. He specializes in client communications. While PD does offer a full range of IT services and consulting, they are currently specializing in website development in PHP/MySQL.

Related posts

• PHP – what it does and what it doesn’t (4)
• Ghacks Web Development PDF Article Compilation January 09 (6)
• Web Development: HTML Playground (7)
• Web development roundup (1)
• Scriptastique web development roundup (4)

We start by creating the bash script first and continue with the cron job after the bash script has been tested to work as intended. All commands in the following paragraphs are executed from the command line.

vi backup.sh

This will create an empty text file in the vi editor. This will be the script that will be executed by the cron job on a daily basis.

bin/sh
/usr/bin/mysqldump -A -u [Username] -p[Password] | gzip > /backups/mysqldump`date +%m_%d_%y`.gz


Press i to enter insert mode and copy and paste the two lines above in the editor. What the script does is to use the mysqldump function to create a mysql backup and store it gzipped in the backups directory using mysqldumpDate.gz as the name with data being the day the backup was created.

The two variables [Username] and [Password] have to be edited and the username and password of a user with sufficient rights entered. It might also be necessary to change the location of the backup folder.

Press ESC to enter command mode and :x to save the file.

./backup.sh

Execute the script to see if it is working correctly. It should create the dump of the MySQL database in the defined directory. It might be necessary to change the permission level of the backup.sh file if you get a permission error during execution.

chmod 755 backup.sh

If the script is working as intended it can be added as a cron job. The following command will open the user crontab list.

crontab -e

If you are in the vi editor you press i to enter insert mode again and add the following line

0 7 * * * /path/to/backup.sh

Please refer to the tutorial for a detailed instruction on how to set the cron job up to suite your needs. This one will execute the script every day on 7am.

It is a good idea to check back after the next execution to verify that everything is working as intended.

Related posts

• Set up MySQL database replication (1)
• Install phpmyadmin for easy MySQL administration (6)
• Database Monitoring Software Db2rss (1)
• Using Cron to Automate Linux Tasks (7)
• Have WordPress back-ups emailed (3)

If you’ve been coding for a while you probably have some set ways in which you work. I recommend you also widen this method to naming variables, which when done consistently can be a huge help, especially when you are using some fancy MySQL along with your PHP code. If you are building a site with 15 MySQL tables it is helpful if you know all the column names because you always name them in the same way, but the same thing goes for simple variables, and even ids and classes for HTML elements.

A very common example can be variables which hold a user’s data. In my case I always use the variable ‘$u’ for holding the username, and the variable ‘$p’ for holding the password. If you are grabbing a lot of data, like first name, last name, email and so on you can make up your own standard set, I use ‘$fn’, ‘$ln’ and ‘$e’ respectively for the three.

Since you usually use these variables in the same script the importance of naming them consistently may not seem like a huge time saver. However when you get into session variables it saves you a lot of time if you don’t always have to look at where you are defining them to find out the names of each. I pull user data using a mysql query when a user logs in and I immediately place the whole array in a session variable name “$_SESSION['user']“. The names of the columns represent the values of this array, so the username and email would respectively become “$_SESSION['user']['Username']“, “$_SESSION['user']['Email']“. This is the same in my case for every single website I build where applicable.

User data naming consistency is also very prominent in the MySQL tables themselves. As you can see above my columns are also named the same in each case, a user’s email is always “Email”, his last name is always “LastName”. I steer clear of abbreviations with MySQL tables so other coders can easily see what’s going on as well. Consistency doesn’t just apply to the actual names, you can also apply it to cases. As you can see all my column names are always capitalized, they are like wikiwords, but user session variables which don’t come from MySQL are not capitalized. For example, when a user logs in he is assigned a time, which is usually one hour. If he/she is inactive for more than this time (no refreshes), he/she is logged out. There is no need to store this in the database, and so I know that this is not in there the session variable here is “$_SESSION['user']['time']“. This means that if I come back to work on a site a year after completion I know exactly where variables come from.

Even if you don’t yet know any PHP, you’re just getting into HTML and CSS you can still use these good practices. When assigning ids and classes to elements try and work out a structure for yourself that you always use. I use empty div tags to clear floats a lot, so I have a separate class named “cl” for this purpose. Whenever I start out a new webpage I include this class by default in the stylesheet since I know I will most likely need it.

That’s about it for standardizing your coding work, most of it is just common sense really. Try and work out your own method which works best for you. It takes time and a lot of practice to get a system working well since there is so much to think of, but if you always keep this in mind somewhere while coding you’ll be a faster and better coder in no time at all!

Related posts

• Web Development: PHP – what role does it fill (1)
• Web development roundup (1)
• Portable Web Server (8)
• PHP – what it does and what it doesn’t (4)
• Local Apache Web Server Wampserver (3)

The web server can be downloaded in various configurations. The various configurations range from a bare-bone Apache web server to a web server supporting MySQL, SQLite, Pearl and PHP. The configuration only has an effect on the type of applications that can be run on the web server. Most users will probably need at least MySQL and PHP support to run their websites locally.

The web server can be started by double-clicking on the Server2Go.exe executable file in the root directory of the server. This will load the various web server modules and display a start page in the web browser. The pms_config.ini file can be used to change various settings of the web server including the default web browser, the port and whether the modules like MySQL or PHP should be started as well.

The actual files of a website are placed in the htdocs directory of the web server. Loading them can be as easy as pointing your browser to 127.0.0.1:4001 or some subdirectory of it depending on the type of site.

MySQL comes with phpMyAdmin which is accessible from the main interface of the web server. Server2Go offers an uncomplicated way to run a web server, it is especially helpful in environments where software installations are restricted.

Related posts

• Local Apache Web Server Wampserver (3)
• How to: Install a LAMP server (7)
• Host your own webserver (18)
• Web Development: Standardizing variables to code faster (18)
• Web Development: PHP – what role does it fill (1)

In this article you will learn how to install and configure the phpMyAdmin MySQL tool.

The first step is to download phpMyAdmin. You can get this tool from the phpMyAdmin download page. Once you have this downloaded you will need to move the file into the document root of your web server (you will need to have root or sudo access to do this and the setup) Most likely this will be either /var/www/html or /var/www. Once you have this file in the proper locaton it is time to take care of business.

The first thing to do is to unpack the file. The unpacking command will depend upon what file format you download. Let’s use the .gz file for an example. With the file phpMyAdmin-3.1.1-english.tar.gz in place issue the command:

tar xvzf phpMyAdmin-3.11-english.tar.gz

The resulting directory will be phpMyAdmin. I highly recommend changing the name of that directory to something easier to navigate and remember. I generally just change the directory with the command mv phpMyAdmin phpmyadmin.

Now that the directory is correct move into the directory. There is one file in particular you must have which is the config.inc.php file. You will notice there is a file called config.sample.inc.php. Some documentation instructs to change the name of config.sample.inc.php to config.inc.php and make your changes from within that file. It is my opinion that method can become confusing with all of the extra options included. Instead create the new config file with the following contents (depending upon your setup):

<?php
$cfg['blowfish_secret'] = ''; /* YOU MUST FILL IN THIS FOR COOKIE AUTH! */
/*
* Servers configuration
*/
$i = 0;
/*
* First server
*/
$i++;
$cfg['Servers'][$i]['user'] = 'root';
$cfg['Servers'][$i]['password'] = 'ROOT_PASSWORD';
$cfg['Servers'][$i]['verbose'] = '';
$cfg['Servers'][$i]['host'] = 'localhost';
$cfg['Servers'][$i]['port'] = '';
$cfg['Servers'][$i]['socket'] = '';
$cfg['Servers'][$i]['connect_type'] = 'tcp';
$cfg['Servers'][$i]['extension'] = 'mysqli';
$cfg['Servers'][$i]['auth_type'] = 'config';
$cfg['Servers'][$i]['AllowNoPasswordRoot'] = true;
$cfg['Servers'][$i]['nopassword'] = true;
?>


There are a few pieces to note. First make sure you use the actual root mysql password where you see ROOT_PASSWORD. Also, if you want to prompted each time for your login information change ‘config’ to ‘cookie’ in the ‘auth_type’ line.

Once you have that configuration file in place you should be able to log into your phpmyadmin system. To do this you will enter http://ADDRESS_TO_SERVER/phpmyadmin/ in your browser (where ADDRESS_TO_SERVER is the IP Address or URL that points to the server.

If, for some reason, this configuration file does not work for you give the web-based setup script a try. To run this point your browser to http://ADDRESS_TO_SERVER/phpmyadmin/setup to start the graphical setup process.

After you are logged in it should be pretty obvious how to create a new database. You simple enter thename you want to give the database and click the Create button.

You’re done! You now have a phpmyadmin install ready to serve you.

Related posts

• Set up MySQL database replication (1)
• Install Drupal on a LAMP Server (2)
• Backup MySQL Databases In Linux Regularly (11)
• PHP – what it does and what it doesn’t (4)
• How to: Install a LAMP server (7)

Backing up seems somewhat of a chore and whilst a cron job can be set up, a WordPress plug-in makes backing up a blog’s mySQL database absolutely hassle free.

WordPress Database Backup allows database backups to be emailed, saved to a hard disk or saved to a server.

Having the back-up emailed may be favourable, especially if you use a service like Gmail with large amounts of storage and reliable hosting.

A useful trick is to set up a Gmail filter to separate backups so quick access is available. Different tables can be backed up, so spam and statistics can be excluded.

Databases can be gzipped, and the SQL file inside the archive can then just be imported should the weblog to be hacked.

Naturally, WordPress Database Backup does not back up files, so images, templates and plugins must be backed up separately.

Related posts

• Set up MySQL database replication (1)
• Lifestream Backup: Free 1 Year Accounts For Ghacks Readers (5)
• Install phpmyadmin for easy MySQL administration (6)
• Database Monitoring Software Db2rss (1)
• Basic postgresql server setup (5)