Pantheon offers a number of ways to connect to your site. In addition to Git and SFTP modes, Pantheon Localdev gives you a graphical interface to your Pantheon sites, complete with a containerized local environment that makes it easy to develop and preview your site locally while still maintaining the Pantheon Workflow.
Localdev lets you use an integrated development environment (IDE) to edit files and code, and push changes to Pantheon right from your desktop. Use it if you want to avoid the command line, or to develop sites with a fully functional local preview, even when you don't have an internet connection.
Localdev is in active development, with new features and updates coming soon.
Create a machine token before you continue.
If you have an older version of Localdev already installed on your machine, remove it to avoid potential compatibility issues. Newer versions of Localdev include support for automatic updates.
Once Localdev is installed, a list of your sites is displayed in a column on the left.
Select a site and click Pull for local development to clone the site locally and boot the local environment.
Since this is the first time you are cloning the entire site code, this will take several minutes. Unless you reset Localdev to its defaults, you will only need to do this once per site.
Each site is cloned to its own directory within
If there are any errors, Localdev will revert all changes and return you to the "Clone your development site" screen. Try the process again, then consult the Troubleshooting section below for how to contact Support.
In the upper right hand corner, click the grey Stopped button and click Start to start the local server.
Once the container has been started, you can preview the site using the Open Browser button in the Local Site section, and track changed files using the Pull and Push tabs.
There are a number of IDEs that have built-in Git tools or plugins available for working with Git from within the IDE:
See your editor's documentation for specific steps on how to commit and push changes from inside the editor.
If you have a Git client that you're already comfortable with, you can use it to track, commit, push, and pull as you normally would. Navigate or point your Git client to track your local code directory, for example:
To have Localdev deal with Git for you, use the Pull and Push tabs.
In Pull tab, check the Pull code option to copy the site's code from the Pantheon Dev environment to your local environment. The Last Pull line below each option's area shows the last time the code was synched.
After you make changes to your site:
Localdev will use the existing
.lando file only when the site is initially cloned. After the initial site clone, there is currently no
lando rebuild equivalent that will force Localdev to reconsider the landofile.
Note that if there are services specified in
.lando, Localdev will return an error.
While Localdev is in beta, support request best practices are especially important for our team to help you resolve the issue, or to report any potential issues in Localdev itself.
Navigate to the Settings tab and confirm that Usage and Crash Data is set to Allow reports. This allows the application to automatically submit crash data to Pantheon Support.
Reproduce the error and note the steps taken.
Report the error:
The steps in this section should only be used as a last resort. This resets Localdev and will remove the machine token and all local copies of your connected sites.
Localdev does not connect to Multidev environments or allow direct database access.