Cookies are short reports that are sent and stored on the hard drive of the user's computer through your browser when it connects to a web. Cookies can be used to collect and store user data while connected to provide you the requested services and sometimes tend not to keep. Cookies can be themselves or others.
There are several types of cookies:
Technical cookies that facilitate user navigation and use of the various options or services offered by the web as identify the session, allow access to certain areas, facilitate orders, purchases, filling out forms, registration, security, facilitating functionalities (videos, social networks, etc..).
Customization cookies that allow users to access services according to their preferences (language, browser, configuration, etc..).
Analytical cookies which allow anonymous analysis of the behavior of web users and allow to measure user activity and develop navigation profiles in order to improve the websites.
So when you access our website, in compliance with Article 22 of Law 34/2002 of the Information Society Services, in the analytical cookies treatment, we have requested your consent to their use. All of this is to improve our services. We use Google Analytics to collect anonymous statistical information such as the number of visitors to our site. Cookies added by Google Analytics are governed by the privacy policies of Google Analytics. If you want you can disable cookies from Google Analytics.
However, please note that you can enable or disable cookies by following the instructions of your browser.
One of the most important rule is to always backup your data with multiple tools on different medium, just in case of.
Just imagine 5 minutes that you lose everything, what you have done in the last 3 months on your homepage..ok still not crying? you loose hundred of hours of work, nightly debugging, customizations, hours of Gimp/Photoshop, lengthy and good written articles...
With Joomla! and now with nearly all CMS, the most important thing to backup is the database. I recommend a daily backup at least!
A script to take daily, weekly and monthly backups of your MySQL databases using mysqldump.
Backup mutiple databases
Single backup file or to a seperate file for each DB
Compress backup files
Backup remote servers
Backup mutiple MySQL databases with one script. (Now able to backup ALL databases on a server easily. no longer need to specify each database seperately)
Backup all databases to a single backup file or to a seperate directory and file for each database.
Automatically compress the backup files to save disk space using either gzip or bzip2 compression.
Can backup remote MySQL servers to a central server.
Runs automatically using cron or can be run manually.
Can e-mail the backup log to any specified e-mail address instead of "root". (Great for hosted websites and databases).
Can email the compressed database backup files to the specified email address.
Can specify maximun size backup to email.
Can be set to run PRE and POST backup commands.
Choose which day of the week to run weekly backups.
Just download the file, save it somewhere, and configure automysqlbackup with your editor of choice (25 first line of file). To test if everything work, just run the file.
automysqlbackup require Mutt
# yast2 -i mutt Mutt (http://www.mutt.org) is a small but very powerful text-based mail client for Unix operating systems. It is used by the script automysqlbackup (sourceforge.net/projects/automysqlbackup/) to cut mail in part (automysqlbackup do ot use mail in that case)
automysqlbackup send daily email with database content, so data are not on host in case of crash or on ftp. You may create 2 emails account and forward the result of the backup to 2 different free email hoster (Gmail and Hotmail for example)
Here is the easiest way to run a daily backup of your database using linux crontab. Thanks to our everyday increasing mailbox size (Thanks Gmail) and their nature to be quite safe for saving document, let’s use them to store the full backup of all our Mysql database! Requirements Having a shell access to your linux box Creating a user with limited mysql rights: SELECT and LOCK_TABLES is enough, For example a user backup_user with a password ChhdeqyqUzd75687fOnmYar Installing Mpack: …
In this small post, I’ll show you how to reset the MySQL password in case you lost it. You’ll need at least the root access of the machine where MySQL run. Reset the MySQL root password Resetting the root password of a MySQL database in case you lost it, is really easy. # /etc/init.d/mysql stop Now start the database in the background, via the mysqld_safe command. Start MySQL with a flag to tell it to ignore any username/password restrictions which …
I found this interesting tool (beside tuning-primer.sh) while trying to optimizing my server setting for #Joomla! mysqlreport mysqlreport makes an easy-to-read report of important MySQL status values. Unlike SHOW STATUS which simply dumps over 100 values to screen in one long list, mysqlreport interprets, formats, and then nicely presents the values in report readable by humans. Numerous example reports are available at the mysqlreport web page. The benefit of mysqlreport is that it allows you to very quickly see a …
According to this MySQL page here, you can win 30 to 50% more performances using MySQL jdbc named pipe! Named pipes only work when connecting to a MySQL server on the same physical machine as the one the JDBC driver is being used on. In simple performance tests, it appears that named pipe access is between 30%-50% faster than the standard TCP/IP access. As default, when you install mySQL on windows using the installer, TCP IP is the default option. …
Digging into mySQL settings can be time consuming, like with any other component. Most of the time, and just by changing a few settings, you can expect a performance increase. The problem is to change what, and to which value. This is where tuning-primer.sh help you: Get this script, http://forge.mysql.com/projects/view.php?id=44 upload it, unzip it, and install it in your /etc folder. Then run it from the command line by entering ./path-to-file/tuning-primer.sh MySQL Server must run a few days or weeks, …
I publish here some of my server settings in the hope that it will also help others... Server Setup AMD64 1 Gb RAM, #Linux OSS 10.0, 7 #Joomla instances (one being waltercedric.com with 250'000 unique visitors per months), 1 simple machine forums, 3 gallery2 install All MySQL tables are myISAM (table locking instead of row loacking in innodb, myIsam make sense as ther is more read then insert) # vi in /etc/my.cnf Below the diff command between a standard MySQL …