Payments are experiencing issues due to temporary restrictions in Russia. If your payment does not go through, please submit a support request.Our support team is available 24/7 — we are always here to help with hosting and server issues.We are now accepting requests for dedicated server rental and colocation services in our data center.Reminder: we recommend enabling backups for additional data protection.A new VPS/VDS lineup with NVMe storage and improved performance is now available.Maintenance work on some servers has been completed. All services are operating normally.
Article3 min read

Selectel Enables Auto-Installation from Custom Images: Why a Standard Server Matters for Your Store

September updates to Selectel's dedicated servers streamline system redeployment. I examine what to include in a server image and why it cannot replace a backup of your orders.

An open server chassis sits on a workbench in a technical workshop.
In this article

The new server is ready, but the store is not yet operational. You must install the OS, extensions, configure services, and recall dozens of minor details that accumulated on the previous machine over years. The more manual steps involved, the harder it becomes to reproduce the result without discrepancies.

Selectel's September updates to dedicated servers now allow automatic OS installation from a custom image. The changelog was updated on September 14, 2026. This feature benefits teams seeking to replicate a prepared environment rather than configuring each machine from scratch.

An image captures the foundation, not the store's activity

A standard image can include a verified operating system and the necessary runtime environment. However, current orders, photos, and catalog updates continue to appear after the image is created. Therefore, a server image and a backup of live data serve different purposes.

For a store running on a CMS, it is critical to record software versions and mandatory extensions. Having the required interpreter without an additional image processing module might allow the homepage to load, but could break photo uploads.

I would divide the verification into two stages: first, reproduce a clean environment, then connect the application and current data. This makes it easier to identify where the error occurred and prevents carrying over random quirks from the old machine.

Do not package someone else's secrets into the image

A production server contains keys, passwords, logs, and temporary files. A mechanical copy can propagate sensitive data and duplicate identifiers. Image preparation should be entrusted to a specialist who understands what must be regenerated upon launch.

Also define who has access to images and how outdated versions are deleted. If any employee can deploy a copy with old credentials, the convenience of automation turns into a management problem.

An image must have a clear validity period. A fixed environment ages: updates are released and application requirements change. Reproducibility is useful only when paired with maintenance of this foundation.

Verify restoration on a blank machine

A reliable test starts with a clean server and ends with a site check. Open the catalog, perform a search, upload an image, verify background jobs, and place a test order. Record the time and manual steps still required.

These steps demonstrate how reproducible the system is. If launching the system requires the memory of a single administrator, the task is not yet complete. A custom image becomes a useful hosting tool when it helps the team calmly replicate a working configuration and maintain it in a comprehensible way.

Discussion0

Share your experience and ask questions. Comments without links appear after editorial review.

No comments yet. Start the discussion.