“Compare Platforms” Before You Decide To Migrate a Drupal Site on Aegir

“Compare Platforms” Before You Decide To Migrate a Drupal Site on Aegir

Create a Fast "Compare Platforms" Migrate Site

Start Your Own "Compare Platforms" Migrate Site

Choose the best tool for the job

Start posting in minutes with:

Unlimited Disk Space

1 Free Domain For a Year

Optimized For "Compare Platforms" Migrate

99.99% Uptime Guarantee

30 days Money back guarantee

The "Compare Platforms" Migrate Special

Special Introductory Offer* For New Customers!

$3.99*2.49€*?1.99*
per month

"Compare Platforms" Migrate Made Simple

"Compare Platforms" Migrate at the Speed of Light

In Aegir , you change your Drupal site by moving it to a different platform . Migration always carries the chance of breaking your website, but Aegir provides an excellent tool for reducing this risk: Compare platforms .

Whenever you click Migrate on the site, you are given a listing of possible platforms. Underneath each platform is a few terms and conditions: Upgrades , Alerts , Errors , and Compare Platforms . These let you know how this target platform compares to the present platform the website is on. Aegir compares each module.

I wish to repeat that. Aegir compares each module. Rather than you needing to search up and write lower each version number, Aegir provides you with an easy table. For every module, the thing is the form of the module around the current platform, and also the form of the module around the target platform.

This table is unbelievably helpful. Having a quick scan, you can observe which necessary modules aren't around the new platform. Or no are missing, or even the wrong version, you are able to fix this before you attempt emigrate (and therefore break) your website.

Extend the Functionality

Upgrades, Alerts, and Errors Every module around the current platform can have as either: exactly the same version, upgrading, an alert, or perhaps an error.

Same version: (blue-grey) When the module has got the same version on the present and target platform, then no attention is required. The module shows as blue-grey.

Upgrades: (eco-friendly) When the module exists around the new platform inside a more recent version, it is really an upgrade. Aegir presumes that this can be a positive thing, and colours the module eco-friendly having a nice little checkmark. From time to time, you don't wish to upgrade a module yet , truly you need to do. Whenever you migrate for this upgraded module, Aegir will require proper care of running necessary database updates behind the curtain. Very helpful. However, upgrades will have issues, which we'll cover in just a minute.

Alerts: (yellow) When the module is missing around the new platform, or contained in a version that's older, or otherwise clearly more recent, this module may show like a warning. Aegir will still let it you to definitely migrate for this platform, however the module might be disabled.

Migration Has Never Been Easier

Errors: (red-colored) Due to how upgrades work, some older versions is going to be unacceptable. The "downgrading" of the module would cause breakage. Aegir identifies this case being an error. When the comparison shows even one error, Aegir won't enable the site emigrate to that particular platform. You are able to compare the platforms, however, you can't choose the woking platform for migration.

Checking Upgrades Generally, upgrades are great, since you want probably the most current form of the module.

However, this will be significant: look for major version upgrades on each module. Minor version upgrades usually have no need for attention, but when a module ranges from single.by to some 2.x, go browse the release notes . That type of upgrade can break things. If there has been major changes, you may want to take extra configuration steps.

Regrettably, Aegir doesn't look for this type of change between version amounts. You have to read each version number by hand, for that current and also the target platforms, while you scan lower their email list.

No Hassle, Just the Fastest "Compare Platforms" Migrate Platform

Or no more compact modules rely on this module , they might also break. When the upgraded version isn't a security upgrade, you may also desire to make a unique platform which (for the time being) doesn't possess the upgraded form of this module, before the more compact modules get caught up and use the upgrade.

No Unnecessary Features, Just "Compare Platforms" Migrate

If you are "freezing" any modules such as this, edit your drush makefile to ensure that it points to particular version.

Add some Necessary Modules for your Platform Fixing alerts and errors is generally easy. First, you have to download the present versions from the missing or outdated modules to sites/all/modules/ . (Learn why you need to put modules in sites/all/modules .)

Obviously, if you have other sites about this platform, you have to stop and save time before you simply start adding or improving modules. Make certain you know how Aegir platforms work . After you have sites on the platform, it must be stable (just like a real platform). Maybe you have to create a new platform and migrate this website to that particular platform rather.

If you are controlling your platform having a drush makefile (highly suggested), then you definitely should also by hand edit this makefile to mirror the additional modules. Should you miss this task, these modules is going to be skipped again whenever you next make use of this makefile to construct a brand new platform.

After you have prepared a platform with the necessary modules, you have to re-verify the woking platform in Aegir. This really is easy: click Platforms , then choose the woking platform, then click on the Verify task. This task informs Aegir concerning the new modules you've just added.

Now return to your site's node in Aegir, and run Migrate and Compare Platforms again. You need to see plenty of Upgrades with no Errors.

Not Every Alerts Should Be Fixed Alerts are tricky. Usually, you need to fix an alert through getting the present form of the missing or outdated module.

But because we have seen, you might have a very good reason for temporarily "freezing" a module in a particular version. You may have to reside using the warning.

Another type of warning develops from a module that's "missing", however that this website does not really use. Remember, for those who have multiple sites on a single platform, each site have a couple of (or many) modules it does not use. Clearly, in case your site does not make use of a module, you are able to ignore an alert it's missing around the target platform.

Migrate When Ready Once you are pleased with your upgrades (and then any alerts), migrate your website towards the new platform. Look for damaged features, but hopefully, your migrated site works all right.