Preparing a Drupal application (glossary term, activate to view definition) for export
Preparing a Drupal application (glossary term, activate to view definition) for export
Before you import your Drupal application to Cloud Platform, perform the
following tasks to prepare your application for the import process. This will
help you better prevent, diagnose, and troubleshoot issues that arise as you
change your hosting environment (glossary term, activate to view definition).
To prepare your application for export:
Perform all outstanding Drupal core and module updates in your
current environment.
Remove any disabled Drupal modules that you aren’t using.
Reconfigure your application to use Memcached. Cloud Platform infrastructure
uses Memcached. If you’re
coming from another hosting provider that uses Redis
or some other storage mechanism, you’ll need to reconfigure your application
to use Memcached.
Test your application by clicking through your application and making
sure features and performance are as expected. Make sure there are no
JavaScript errors in your browser’s console. Check the error logs to
ensure that everything is running correctly.
Make sure you do not have a PHP memory limit set in your .htaccess or
Drupal settings.php files. If your application is configured with a
larger PHP memory limit than the memory limit configured on your
Cloud Platform infrastructure, it won’t be able to start up.
Large files or directories in your
docroot, such as /photo or
/video, can cause problems when you send your codebase to
Cloud Platform. Cloud Platform can fail when it attempts to send your code
with large files to its infrastructure.
Move these files and directories to a .
Did not find what you were looking for?
If this content did not answer your questions, try searching or contacting our support team for further assistance.
Before you import your Drupal application to Cloud Platform, perform the
following tasks to prepare your application for the import process. This will
help you better prevent, diagnose, and troubleshoot issues that arise as you
change your hosting environment (glossary term, activate to view definition).
To prepare your application for export:
Perform all outstanding Drupal core and module updates in your
current environment.
Remove any disabled Drupal modules that you aren’t using.
Reconfigure your application to use Memcached. Cloud Platform infrastructure
uses Memcached. If you’re
coming from another hosting provider that uses Redis
or some other storage mechanism, you’ll need to reconfigure your application
to use Memcached.
Test your application by clicking through your application and making
sure features and performance are as expected. Make sure there are no
JavaScript errors in your browser’s console. Check the error logs to
ensure that everything is running correctly.
Make sure you do not have a PHP memory limit set in your .htaccess or
Drupal settings.php files. If your application is configured with a
larger PHP memory limit than the memory limit configured on your
Cloud Platform infrastructure, it won’t be able to start up.
Large files or directories in your
docroot, such as /photo or
/video, can cause problems when you send your codebase to
Cloud Platform. Cloud Platform can fail when it attempts to send your code
with large files to its infrastructure.
Move these files and directories to a /files directory for your
application, such as .
/files
directory for your
application, such as
[docroot]/default/files
. After you move the files
and directories, you can make symlinks to their relative locations on your
local infrastructure, which will be maintained after you send your
application to Cloud Platform. For more information, see
Make a full back up of your application and store this copy in a safe
place. Verify that you can revert to your backup copy.
[docroot]/default/files
. After you move the files
and directories, you can make symlinks to their relative locations on your
local infrastructure, which will be maintained after you send your
application to Cloud Platform. For more information, see