simplest way to install FFmpeg on CentOS

After heading to the official ffmpeg download page, click the link under Linux Static Builds.

Click the appropriate (32- or 64-bit) and desired (snapshot or numbered) release to download.

If the libav version of ffmpeg was installed, remove it. The two can not reside on the same machine.

Extract the files (and two directories) as follows:

  • For single-user systems: to $HOME/bin
  • For multi-user setups: to /usr/local/bin

Static build install is done and ffmpeg is ready to use.

% wget
% tar xJvf ffmpeg-git-64bit-static.tar.xz
% cd ffmpeg-git-20150427-32bit-static
% ./ffmpeg

maybe useful!

yum install xz

Automatic Database and file Backup with PHP

phpMyBackup Pro is a very easy to use, free, web-based MySQL backup application, licensed under the GNU GPL.
You can create scheduled backups, manage and restore them, download or email them and a lot more!

Major features:

– backup of one or several databases with or without data, table structure, …
– three types of compression (no compression, gzip or zip)
– scheduled backups (by a small PHP script which must be included in an existing PHP script)
– interface for managment of the backups (viewing, restoring, downloading, deleting)
– backup directly onto FTP server and sending of backups by email
– platform independent – only webserver and PHP needed to run e.g. on MS Windows, Linux or Mac
– shell mode (to use manually or by cron script)
– backup of whole file directories (on a FTP server).
– backup databases from different accounts on several MySQL servers
– one installation can be used for all MySQL users of one MySQL server (used by webhosters)
– highest security through two alternative login methods (HTTP or HTML authentication)
– easy to use interface and very easy to install
– several language packages available
– online help (included in pMBP) and FAQ on this website


to automate it, you must set cron like this:

wget -O /dev/null

NIC EPP Server

For communicating with NIC servers you must use EPP. Here is a brief start point for you!

EPP (Extensible Provision Protocol) defines an unified way how registrars can communicate with registries of domain names by exchanging XML messages.

EPP is typically implemented as an API between the registrar’s web interface and the Registry. Such integration allows registrar to react immediately to requests from it’s clients and know for sure if the action succeeded or not. Should some action, such as registration of a domain name, to be put off until later, the registry will notify registrar with the service message.

What benefits are from using EPP?

  • Once a client software is implemented, it becomes more easy to integrate it with other registries and offer a wider range of top-level domain names to your clients.
  • Requests from your clients can be performed automatically and 24/7

EPP overview

  • A typical EPP conversation starts when client connects to the server using SSL.
  • Server responds with a “service menu” with offered services and extensions available languages etc.
  • Client logs in using it’s account name and password and chooses services and other options for conversation from the offered ones.
  • Client polls the server for unread notifications and retrieves them if any.
  • Client reads details, creates new or updates existing contact persons, domain names and associated networks as needed. Server responds immediately with a well defined response code, reflecting the status of requested object.
  • Client waits for new things to be done, periodically polling for notification messages to keep session alive.
  • Connection is ended either by client when all is said and done or by the server if session timeouts.

EPP protocol describes both synschronous and asynchronous operation modes, But most of NICs offer EPP service only in synchonous mode (client receives answer for each request and only then sends next command to the server).

Here is a more detailed documentation.

Cpanel API Digest

Hello every one! Let’s eat some tricks…


Cpanel Security token

“Security token” URLs were added in cPanel & WHM 11.25 as a security measure, and they were enabled by default in version 11.28. They help combat a common type of attack called a Cross-Site Request Forgery (XSRF).

So, what does a “security token” look like? Take, for example, this URL:

With security tokens enabled, this would become:

The token is available in the environment variable ‘cp_security_token’.

my $APIurl = "$ENV{'cp_security_token'}/xml-api/$url";

Find more information click here.