Table of Contents
Table of Contents |
---|
...
Multidev
...
Preparing for a request
Management
In order for you to get your changes up so we can test them, you need to deploy a Multidev and apply your changes there first. Once your changes are on the Multidev, test them against the latest available upstream updates. Then a Merge Multidev to Dev request needs to be submitted in your college Slack channel. You can expect your changes to be on the development environment by the end of the next business day. After your changes pass our code review process we will apply your changes to the staging/test environment for further review. Expect your changes to move from stage to the production environment usually with the next morning code push if everything goes well with the further review on stageto interact with a Multidev you must have a developer account setup for your college website on the Pantheon platform. These accounts are created by the ITS Web Team, the site owner needs to request developer access via email or Slack.
...
Creating a Multidev
More In depth information about Multidev environments is available in the Pantheon documentation. When a Multidev is created, a branch is also created with the same name.
Login to your Pantheon Dashboardthe Pantheon dashboard for your college
Click the Multidev tab
Click the Create an Environment button
On the Create Multidev Environment modal that pops up, Name the New Environment and Git Branch and under the Cone Database and Files From: drop-down select a database.
Click the Create Environment button
Wait
Once it is done you will see:
Click the name of your Multidev to open its dashboard
...
Launching
...
a Multidev Site
Starting NotesYou can visit the URL presented when you first created the Multidev, or follow this step below.
On your Multidev dashboard, click the Visit {{ name of your Multidev }} Site button
Info |
---|
The URL will work until the Multidev is deleted. The URL is public facing and can be locked if needed. |
...
Locking a Multidev
When a Multidev is created, it is public facing, anyone with the URL can view it unless it is locked. This step is not required and can be used at your discretion.
From your Multidev dashboard, click the Security option on the left menu
In the Environmental Access section, click the Locked button
Enter a Username
Enter a Password
Click the Lock Environment button
...
Unlocking a Multidev
If your Multidev is locked, only users with the Username and Password you set can view your site.
From your Multidev dashboard, click the Security option on the left menu
In the Environmental Access section, click the Public button
...
Cloning a Multidev
...
Locally Using Git
To accomplish this step, you must already have installed Git on your computer.
Click the Clone with Git button
Click the Show Detailed Instructions link
Follow Use the steps in the Example section to familiarize yourself with the Git commands required to make your changes and push them back into the Multidev
Info |
---|
Visit the Local Development Stack article to read more about testing your changes locally. |
...
Deleting a Multidev
Starting NotesWhen a Multidev is no longer needed, it is safe to delete the environment.
Navigate to your Pantheon dashboard
Click the drop down arrow on the Multidev tab
Click Multidev overview
Click the Delete Environment button
Type DELETE in the text box
Click the Delete the {{ Name of your Multidev }} Environment button
...
Related Articles
Select the table below to edit…
...