This section provides answers to frequently asked Multidev questions.
Multidev is available to all organizations and users with Gold Accounts and above, as well as their supporting partners and agencies.
Multidev environments that are already created on a Pantheon site are available to all users with access to the site.
You can create a new Multidev if you:
Belong to a Gold Account or above
Support a site that is owned by a Gold Account customer or above
Site admins of an organization with Multidev can invite independent contractors or set an agency as a supporting organization. The Pantheon system will automatically choose the highest account tier among the group. This logic makes Multidev features, including the ability to create Multidev environments, available to the supporting organization or the site team members on the associated sites.
If you meet the conditions and still don't have access to an existing Multidev or the ability to create a new Multidev, please contact Support.
Each site has a limit of 10 Multidev environments.
Autopilot creates and uses a Multidev environment that does not count towards the total limit.
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. 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 (for example,
git push origin example-br) then navigate to Multidev then 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.
Multidev environments spin down after approximately 60 minutes of idle time. Refer to the Idle Containers documentation for more information.
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.