For information about what Multidev is and how to use it, see our full guide on Multidev.
Pantheon is extending our COVID WebOps offer to qualified government, medical, or educational institutions with a crisis communications website, and to non-profit organizations directly providing relief.
We launched this initiative at the beginning of the COVID-19 pandemic to support organizations responding to the pandemic or delivering vital information to the public. It's since evolved to include a pre-built response site to allow organizations on the COVID-19 front lines to deploy rapidly and deliver emergency communications.
Multidev is available to all Gold Accounts and above. Organizations with Multidev can assign unprivileged users who can access Multidev environments. See Change Management for more information about roles and permissions.
Users have access to Multidev if they:
- Have been assigned a role as a member of an Organization that has the Multidev Feature (like a Pantheon Preferred Partner).
- Are a Direct Online Gold Account customer or above.
If you fully meet either of these conditions and still don't have access to Multidev, please contact support.
Each site has a limit of 10 Multidev environments.
Elite sites can request additional Multidev environments from support as needed.
No; each branch environment can be independently set to use either SFTP or Git mode for code changes.
At this time, there are no permissions or access controls for managing the deployment and development workflow beyond the existing team functionality. This is a known feature request and is scheduled for a future release.
Branch names can contain any ASCII letter and number (a through z, 0 through 9) and hyphen (dash). The branch name must start with a letter or number. Currently, the maximum length is 11 characters and environments cannot be created with the following reserved names:
Yes, you can; your Git repository is not restricted. If you do not use Multidev, then the interface will not show the branches, allow creation of an environment for a branch, and so forth.
Yes. Push a new branch from your local (e.g.,
git push origin example-br) then navigate to Multidev > Git Branches from your Site Dashboard and select Create Environment next to the branch name.
There is no limit on the number of branches you can have in your Git repository. The limit on Multidev environments is 10 per site.
Yes, you can assign custom domains to each Multidev environment.
You can use any Git client with Multidev. Use of the command-line Git client is recommended for compatibility with Dashboard instructions.
At this time, Multidev on Pantheon will only work with the Pantheon hosted code repository. You can use remote repositories with your workflow, but Multidev on Pantheon will only recognize changes pushed to Pantheon.
Is there a public API available for post-commit hooks or other integrations with external project management systems?
No, but developers can use Quicksilver hooks to integrate Multidev creation and other workflows with external services.
Yes, you can backup and restore a branch environment. However, if you restore an old version of code in Dev, you may damage Multidev environments.
If the organization changes to a plan that doesn't feature Multidev, you will still be able to access existing Multidev environments, but will not be able to create new ones.
Users encounter this error with sites that use the MyISAM engine with a varchar index that exceeds 767 bytes. To resolve, convert MyISAM tables to InnoDB.