DataLife Engine (DLE) hosting: requirements and setup

DataLife Engine is a commercial PHP content management system built for news sites, media portals and blogs, popular mainly in Russian-speaking countries. Hosting it is the familiar PHP routine - files in a web root, a MySQL-family database, an installer in the browser - with three things that are specific to DLE: you need a licence for each domain (or the limited free demo), friendly URLs depend on rewrite rules written for Apache, and the support community and most documentation are in Russian.

According to the official requirements page, current versions need PHP 8.0 or newer, MySQL 5.6+ or MariaDB 10.0+, nginx or Apache, and the PHP extensions zlib, xml, gd, curl, mbstring, fileinfo, exif and intl. Those figures are minimums; real sites should run a current PHP 8 release and a current database. This guide goes through the licence, the install, the configuration files, nginx, caching (including Redis-protocol caching on Valkey), updates and the problems people actually report.

What DLE is, and the licence#

DLE is developed by SoftNews Media Group and sold from its official site, dle-news.ru. It is closed-source commercial software in the sense that matters for hosting: you cannot download a full version freely, and the licence is tied to a domain.

As the official site describes it at the time of writing, there are three ways to run it:

Each licence covers one domain; a second site needs a second licence. Prices and terms change, so read the current purchase page before buying rather than trusting any figure in a blog post, this one included. The demo has no time limit, which makes it a reasonable way to check that DLE runs on a given hosting plan before paying.

One warning deserves its own paragraph. Because DLE is commercial and popular, "nulled" copies - pirated versions with the licence check removed - are everywhere, often bundled with templates and modules on download sites. They are the single most common way DLE sites end up compromised: the people who remove a licence check are rarely shy about adding a backdoor. Install only a version downloaded from your account on the official site, and buy third-party modules and templates from their developers.

Requirements and sizing#

The official requirements page is the authority and is updated with releases; check it for the version you are installing. In summary:

The low official memory figure describes what the engine itself needs per request, not a site. A news portal with thousands of articles, comments, a busy front page and a few modules is a different matter: PHP workers, the database's own memory and the cache all share the plan. As a rough guide:

Disk use is dominated by uploads/ - images attached to news items - and by backups kept on the server. Keep an eye on both. How much RAM WordPress needs walks through the same arithmetic for another PHP CMS, and it applies here almost unchanged.

Before uploading anything, confirm the PHP version and extensions your hosting actually provides. A file containing <?php phpinfo(); in the web root, loaded once and then deleted, lists both. The official FAQ notes that an install.php showing only "Internal Server Error" usually means a required PHP module is missing.

Installing DLE#

1. Create the database and a user with full rights on it. Write down the host, port, database name, user and password.
2. Upload the site files. The distribution separates the files that belong on the server from the documentation; upload the contents of the site folder into your web root, not the folder itself, or the site will only answer under a subdirectory. Upload the archive and unpack it with the file manager rather than sending thousands of files over SFTP one by one - SFTP and the file manager covers both routes.
3. Check permissions. The installer tests that DLE can write to the directories it needs - among them backup/, uploads/ and its subfolders, templates/, engine/data/ and engine/cache/. Fix anything it flags. On container-based hosting, where PHP and the file manager run as the same user, this usually passes without changes.
4. Run the installer at https://example.com/install.php. Accept the licence, let it check the environment, enter the database details and create the administrator account. Use a non-obvious username and a generated password.
5. Delete `install.php` when the installer tells you to. A leftover installer is an invitation to reinstall over your site.
6. Activate the licence following the instructions in your account on the official site, if you bought one.

The administration panel is at /admin.php. DLE supports renaming that file to something less obvious, which cuts out a lot of automated login attempts; follow the steps for your version, because the panel's own links must be updated to match.

On RE:NODE, DLE is one of the systems the Engines plans are sized for. You install it yourself, through SFTP or the file manager - there is no one-click installer - and each plan carries two database slots created from the panel with a generated host, user and password, so the database exists before you start step 1.

The configuration files#

DLE keeps its settings in PHP files under engine/data/. Two matter most.

`engine/data/dbconfig.php` holds the database connection, written by the installer:

define ("DBHOST", "db.example.internal:3306");define ("DBNAME", "dle");define ("DBUSER", "dle_site");define ("DBPASS", "from-the-panel");define ("PREFIX", "dle");define ("USERPREFIX", "dle");define ("COLLATE", "utf8mb4");

When you move the site to a new server, this is the file to edit. As with any PHP application, localhost is only right when the database runs on the same machine; otherwise use the hostname you were given, with the port if it is not the default. Check the exact format your version writes before editing it by hand - the installer's own output is the template.

`engine/data/config.php` holds the settings you change in the admin panel, under System Settings: site address, language, time zone, friendly URLs, caching and much more. Change them through the panel where possible; the panel writes the file. If a bad setting - most often a wrong site address - locks you out, this is where you fix it by hand.

Both files contain secrets or settings that reveal how the site works. They are PHP, so a correctly configured server executes them rather than displaying them; never leave copies with other extensions, such as dbconfig.php.bak, which would be served as plain text.

Character set matters for DLE sites with history. Older sites were often built in windows-1251; current versions use UTF-8. Moving an old site means converting both the database and the templates, and getting it wrong produces the familiar garbled Cyrillic. Do the conversion as a separate, tested step - never as a side effect of a server move.

Friendly URLs on nginx#

DLE's search-engine-friendly URLs - /news/12-site-launch.html instead of index.php?newsid=12 - are produced by rewrite rules in the .htaccess file shipped with the engine. On Apache with mod_rewrite, they just work.

nginx ignores .htaccess. Friendly URLs on nginx need those rules translated into nginx location and rewrite directives, and DLE's rule set is long because each URL type (news, categories, static pages, tags, user profiles, RSS) has its own pattern. Two cautions apply:

• Translate the rules from your own version's `.htaccess`, not from a snippet copied from a forum post about a different release. The patterns change between versions.
• Make sure rewritten requests still reach PHP. A common failure, reported often on DLE and nginx forums, is a translated rule that ends up serving index.php as a download instead of executing it. Rewrites must lead into the location that passes .php requests to PHP-FPM.

At minimum, the front-controller fallback every PHP CMS uses should be present:

location / {    try_files $uri $uri/ /index.php?$args;}

That alone does not make DLE's friendly URLs work, because DLE maps paths to specific query parameters. If you cannot edit the nginx configuration on your hosting, switch friendly URLs off in System Settings - the site then uses index.php?... addresses, which work everywhere - and ask your host whether the DLE rules can be added. Turning friendly URLs on or off after a site is indexed changes every address, so decide before launch.

The certificate and domain come first, before you set the site address in the panel: on RE:NODE, the proxy slot issues and renews the certificate once your A record points at it. Your domain and its certificate covers the DNS side.

Caching, including Redis on Valkey#

DLE caches generated blocks and pages, and on a busy news site caching is the difference between a database that copes and one that does not. The settings are in the admin panel under System Settings, on the Optimisation tab: switch caching on, then choose the cache type.

Redis caching arrived in DLE 14.2 and lets you enter the server address, port and authentication details in the same panel. Valkey speaks the same protocol as Redis, so a Valkey server works as the Redis cache backend. The precondition is the PHP extension: if phpinfo() shows no redis section, the Redis option cannot work on that hosting, whatever you configure in the panel. File caching is the right choice in that case, and it is perfectly adequate for most sites.

Two habits keep caching from causing confusion. After changing templates, clear the cache from the admin panel so visitors do not see old output. And size the cache honestly: with an external cache, DLE stores blocks that are rebuilt on a miss, so an evicting policy on the Valkey side is appropriate - Valkey memory and eviction policies explains the options.

Backups and updates#

DLE includes a database backup tool in the admin panel, writing dumps into the backup/ directory. It is useful and not sufficient on its own: the dumps sit on the same disk as the site, and they do not include uploads/, templates or configuration. A real backup is the database plus the whole file tree, stored somewhere else, and restored occasionally to prove it works - backups that actually restore is the case for that last step.

Updates come as new releases on the official site, with an update procedure that replaces the engine files and runs a script that upgrades the database structure. Follow the instructions shipped with each release exactly, and before every update:

1. Take a full backup of files and database, and check it completed.
2. Note every file you changed by hand - templates, core files edited for a module. An update overwrites core files, and your edits go with them.
3. Check that each third-party module supports the new version. Modules that patch core files are the usual reason an update breaks a site.
4. Update a copy of the site first if you can; on hosting with two database slots, a staging copy with its own database costs nothing extra.
5. Apply the update, clear the cache, and test publishing, comments and login.

The basic licence includes updates for a year. After that, the version you have keeps working, but you stop receiving new releases - including security fixes - until you renew. Factor that into the cost of running DLE.

Troubleshooting#

`install.php` shows "Internal Server Error". A missing PHP extension, per the official FAQ. Compare phpinfo() with the requirements list.

Database connection error after a move. engine/data/dbconfig.php still has the old host or password.

All pages except the home page return 404. Friendly URLs are on and the rewrite rules are missing - typical on nginx. Translate the rules or switch friendly URLs off.

Garbled Cyrillic text. A character-set mismatch between database, connection and templates, usually after moving an old windows-1251 site.

Admin panel redirects to the old domain. The site address in engine/data/config.php was not updated after a domain change.

The Redis cache option does nothing. The php-redis extension is not loaded, or the address, port or password is wrong.

FAQ#

Can I use DLE for free?

Only the demo version, which is limited to 100 news items and 200 comments, has encoded source and receives no updates or support. A real site needs a paid licence for its domain. Avoid "free full versions" from download sites; they are pirated and frequently backdoored.

Does DLE work on nginx?

Yes - the official requirements list nginx alongside Apache. The only difference is friendly URLs, whose rules ship in Apache's .htaccess format and must be translated for nginx, or friendly URLs switched off.

Can I move a DLE site to a different domain?

The licence is per domain, so contact the developer about moving it before you switch. Technically, the move means updating the site address in the configuration and replacing old domain references in the database, after a full backup.

Which PHP version should I use for DLE?

The newest PHP 8 release that your DLE version and every installed module support. The official minimum is 8.0, which is out of support upstream; old modules are the usual reason a site is stuck on an older version.

Do I need a separate cache server?

Not for most sites; file caching is built in and works anywhere. A Redis-protocol cache such as Valkey helps busy sites by taking load off the disk and database, provided the hosting has the php-redis extension.