here is a simple deployment shell script (.sh) using rsync to deploy your local application to a productive location.

You can download it here.

Follow the README file for setup and usage.

Feedback comments are always welcome :)

$>file.ext

You’re actually just putting a null content on the file, but it’s a very effective way to quickly clear a file contents on unix, especially if you want to keep permissions, etc.

Very useful for clearing error logs.

1. Get the main packages

(check) http://dag.wieers.com/rpm/packages/yum/

$wget http://dag.wieers.com/rpm/packages/yum/yum-2.4.2-0.4.el4.rf.noarch.rpm

(check) http://rpmfind.net/linux/rpm2html/
search.php?query=libsqlite.so.0&submit=Search+…&system=&arch=

$wget ftp://fr2.rpmfind.net/linux/PLD/dists/ac/ready/i386/libsqlite-2.8.15-1.i386.rpm

(check) http://rpmfind.net/linux/rpm2html/
search.php?query=python-elementtree&submit=Search+…&system=&arch=

$wget ftp://rpmfind.net/linux/dag/redhat/el4/en/i386/dag/RPMS/python-elementtree-1.2.6-7.el4.rf.i386.rpm

(check) http://rpmfind.net/linux/rpm2html/
search.php?query=python-sqlite&submit=Search+…&system=&arch=

$wget ftp://rpmfind.net/linux/dag/redhat/el4/en/i386/dag/RPMS/python-sqlite-0.5.0-1.2.el4.rf.i386.rpm

(check) http://rpmfind.net/linux/rpm2html/
search.php?query=urlgrabber&submit=Search+…&system=&arch=

$wget ftp://rpmfind.net/linux/dag/redhat/el4/en/x86_64/dag/RPMS/python-urlgrabber-2.9.7-1.2.el4.rf.noarch.rpm

2. Install Rpm’s

$rpm -ivh libsqlite-2.8.15-1.i386.rpm
$rpm -ivh python-elementtree-1.2.6-7.el4.rf.i386.rpm
$rpm -ivh python-sqlite-0.5.0-1.2.el4.rf.i386.rpm
$rpm -ivh python-urlgrabber-2.9.7-1.2.el4.rf.noarch.rpm
$rpm -ivh yum-2.4.2-0.4.el4.rf.noarch.rpm

3. Setup the Repository
(check) http://dag.wieers.com/rpm/packages/rpmforge-release/

$wget http://dag.wieers.com/rpm/packages/rpmforge-release/rpmforge-release-0.3.6-1.el4.rf.i386.rpm
$rpm -ivh rpmforge-release-0.3.6-1.el4.rf.i386.rpm

4. Yum update all packages

$yum update

$uname -m

uname -s

Linux Systems return “Linux”.
The Macs, for example, return “Darwin”.

- “$cat /etc/redhat-release” will show you information for red hat based distros.

- “$cat /etc/SuSE-release” for SUSE based distros.

- “$cat /etc/mandrake-release” for mandrake distros.

- “$cat /etc/debian_version” for debian based distros.

- “$cat /etc/UnitedLinux-release” might also return some more information.

I also found this useful tip at linuxhelp.net:
You *might* get some clues by running “uname -r” which will show you kernel version – Some ditributors will rename the kernel to make it specific to their distro (eg, RHEL kernels have RHEL in their name)

Note:  As pointed out by Ricardo “$cat /etc/debian_version” won’t return the distro itself, but the version of the distro. Sorry :/

$cat /proc/version

Go to How to check Linux Distro from command line for more information.

Storage engines differ essencially in how they organize the data, indexes, caching, etc.
The pratical results are different possibilities in data organization and restrictions (foreign keys, constraints, triggers (on delete, on update), etc) as well as different performance capabilities.

Technical Differences:

MyISAM is designed to be a simple and effective storage engine, ideal for small websites, blogs, etc. Doesn’t require much technical knowledge and get’s the work done. It also features full-text index, allowing you to take advantage of the very useful “MATCH col AGAINT(‘needle’)” text search clause.

MRG_MyISAM is treated as MyISAM but can be “shared” among different databases – very useful for main tables in multiple-database applications, as long as your working on the same MySQL server.

InnoDB is designed to be more of a storage engine for applications. It features foreign keys, triggers, etc – essential for multi-million rows and organizational data.

Performance:

A few years back MyISAM would kick ass on SELECT clauses, whereas InnoDB was usually better for heavy INSERT / UPDATE and DELETE clauses.
These days InnoDB can be even faster than MyISAM for SELECT clauses.

Though MyISAM can be much faster for a simple “SELECT count(*) from table” query as it caches the amount of rows on a table, they work more or less the same when you use the “where some_col=’some_val’” clause. On the other hand text searching on full-text index kicks ass over any “LIKE ‘%needle%’ ” clause.

MRG_MyISAM is pretty much like MyISAM, though it can usually get a little bit slower due to multiple database usage and locking.

All in all InnoDB has come a long way these past few years, and has become my first choice for applications, though i still use separate MyISAM tables for full-text searching on text fields.

In Mac OSX versions 10.5.2 and later:
$ dscacheutil -flushcache

In Mac OSX versions 10.5.1 and before:
$ lookupd -flushcache

this issue came to me after i got “Can’t connect to local MySQL server through socket ‘/var/mysql/mysql.sock’” on a mysql connection on php on a fresh installed mac – php connect’s correctly to 127.0.0.1 , but does not connect to localhost .

On a mac the default mysql socket is ‘/private/tmp/mysql.sock‘ and not ‘/var/mysql/mysql.sock’, you can confirm it by using $ locate mysql.sock on a Terminal.

So basically you have to change the php default connection socket to mysql to ‘/private/tmp/mysql.sock‘ . To do this you have to edit your php.ini – probably located at ‘/private/etc/php.ini‘ – via:

• $ sudo nano /private/etc/php.ini
• ctrl+w (where is) “mysql.default_socket“
• alter to “mysql.default_socket = /private/tmp/mysql.sock”
• crtl+x followed by y and enter to save php.ini
• $ sudo httpd -k restart to restart Apache 2

Retry connecting to mysql localhost on php – should be working :)

Update:
if you use mysqli you also must set “mysqli.default_socket = /private/tmp/mysql.sock” on php.ini;