This section provides information on email and media support on the Pantheon platform.
Pantheon has a cloud-based infrastructure, which means that we cannot ensure the high deliverability of emails originating from your Application Containers, as they have no fixed location.
All sites have access to a local Postfix service for testing and development, however we recommend using an external SMTP gateway (for example SendGrid) in production to ensure that your email is delivered.
We do not support ffmpeg transcoding, and we do not have plans to add this feature. However, it is possible to run a site on the platform and integrate with a third-party transcoding service or multimedia platform that lets you create streaming-optimized videos. Those providers have optimized the highly complex process of transcoding and serving video content, and leveraging their infrastructure is often preferable to a custom solution.
Emoji support is available out of the box on WordPress and Drupal. Drupal 7 sites can enable Emoji support by following this procedure:
For new or existing Drupal 7 installs:
- Add the following lines to your
$databases['default']['default']['charset'] = 'utf8mb4'; $databases['default']['default']['collation'] = 'utf8mb4_general_ci';
For existing sites that already have an active database:
Install the UTF8MB4 Convert Drush command and convert the database. Note that this is not a Drupal module that can be enabled, it's a Drush command that should be placed within
Clear Drush cache using Terminus after you've installed the command in
/sites/all/drush. This allows the new command to run.
terminus drush <site>.<env> -- cc drush
Create a backup of the site database, then place the site in maintenance mode and run the following command:
terminus drush <site>.<env> -- utf8mb4-convert-databases
This will convert the database tables in the existing installation to the correct encoding to support emoji characters. Place an emoji in the site text to test the conversion.
HTTP range requests enable sending only a portion of an HTTP message from server to client, and are typically used to speed viewing of large media such as:
- Video background images
- Streaming content such as:
- Videos with pause and resume functions
Byte-range request header parameters are not supported on Pantheon. Modules and plugins that require specified byte-ranges will not work.
Highly populated directories can cause a small decline in performance at around 50,000 files in a single directory, and a significant performance drop at over 100,000 files. Refer to Highly Populated Directories for more information on how to refactor your file structure.
Image optimization libraries have to be installed on the server, including:
At this time, they are not supported. For more information see Modules with Known Issues.
However, you can run a great streaming media website. Pantheon recommends that you find a service to handle the transcoding and streaming, whether that's YouTube, Brightcove, Vimeo, Soundcloud, or another provider. These services provide all the necessary components for great streaming media.
It is also possible to deliver smaller media files from Pantheon using progressive download, but the media will not automatically adapt to the bandwidth and capabilities of the device browsing the site, nor does Pantheon support "seeking" to arbitrary playback positions based on time. The actual media formats (encodings, containers, file name extensions) are unrestricted.