WordPress is the most popular CMS in the world today, powering more than 74 million websites in the world and 47% of all websites using a CMS. It’s giving birth to dozens of millions of new posts and comments each month, and that’s just the tip of the iceberg. WordPress also dominates application installations in Plesk – in fact, it comprises almost two thirds of all known applications installed on Plesk servers. After looking at all these numbers, it should not be a surprise for any person involved in hosting industry that we have decided to address the growing market of WordPress users by adding a tool that helps them manage and secure their blogs. Enter WordPress Toolkit, available in Plesk 12:
In this article I will explain the ways WordPress Toolkit helps WordPress hosters and users, address some misconceptions, answer several frequently asked questions, and share some spoilers about what’s to come in the next versions of WordPress Toolkit.
We will use an Ubuntu 14.04 server and Plesk 12.0 for our experiments. I assume that you will get this configuration somehow.
Plesk may use Apache and Apache+nginx for serving of websites. In the scope of this article we’ll check how to setup Django apps hosting only for Apache without nginx.
Plesk 12.1.8 early preview is available. This build is not for production usage, only for demonstration purposes.
Preview release highlights:
- Fully reworked Databases screen. Many features were improved and many new were added. The most notable: Read the rest of this entry »
In this article I’ll try to explain how to run Ruby on Rails applications on a server managed by Plesk. Plesk itself does not support modern Rails apps natively. But this doesn’t mean that you cannot deploy such applications to Plesk hosting.
We will use an Ubuntu 14.04 server and Plesk 12.0 for our experiments. I assume that you will get this configuration somehow. It’s possible to deploy Rails apps on different OS and using different Plesk version, but all further commands will rely on Ubuntu 14.04 and Plesk 12.0 capabilities. Read the rest of this entry »
Dropbox Backup is a Plesk extension that extends the built-in Backup Manager and allows you to use Dropbox storage. Read more about the extension in the previous post.
A new version of the extension was recently released. It is available in the Extensions Catalog. In this post, I would like to announce new features implemented in this version. All of them are based on the feedback collected from the blog and the forum. Please continue providing your ideas.
The extension is compatible with Plesk since version 11.5 on both Linux and Windows platforms.
There might be cases when a Plesk server is located in a private network and it has only one internal IP address. In such cases, website visitors can access the hosted sites via the NAT technology. NAT translates public IP addresses into internal IP addresses and encapsulates this information in network packets.
Plesk uses one and the same IP address for various purposes. For example, an IP address is used for web hosting (Apache + nginx configuration files) and for DNS zone definitions. And here is a problem. In the former case, an internal IP address should be used, and in the latter case, an external IP address. Plesk UI shows only one IP address, but it does not let you configure the mapping (translation) of IP addresses.
We’ve always strived to keep Plesk visually modern and pleasant for users, so we have created a new additional skin for Plesk 12. We would love to hear your opinion on this skin, as we’re evaluating it as a possible replacement for current default Plesk skin.
Although there was no official announcement yet, Plesk 12.0 was released and is already available for deployment. The general availability mark will be set a little bit later, but now this release is in the “early adopter” stage. This means that you can install it right now and start using the new features.
This article describes how to setup a development environment for creation of Plesk extensions.
Creation of a new Plesk extension can be started from generating a new stub. To do this log in to a machine with Plesk installation and type the following command:
# plesk bin extension --create my-extension
Here is an example of output:
The extension was successfully created.
The path to extension's entry points: /usr/local/psa/admin/htdocs/modules/my-extension/
The path to PHP classes: /usr/local/psa/admin/plib/modules/my-extension/
The path to installation scripts: /usr/local/psa/admin/plib/modules/my-extension/scripts/
The path to the directory with run-time data: /usr/local/psa/var/modules/my-extension/
This command will create a new extension named “my-extension”. It will also provide information about where extension parts are located on the file system.