![]() Its construction began in 1878, in a location south of the old Bori Bunder railway station, and was completed in 1887, the year marking 50 years of Queen Victoria's rule. The terminus was designed by a British born architectural engineer Frederick William Stevens from an initial design by Axel Haig, in an exuberant Italian Gothic style. Mumbai CSMT (Maharashtra) Show map of MaharashtraĬhhatrapati Shivaji Maharaj Terminus (previously Chhatrapati Shivaji Terminus, Mumbai station code: CSMT ( mainline) / ST ( suburban), is a railway terminus and UNESCO World Heritage Site in Mumbai, Maharashtra, India. Mumbai–Chennai line Mumbai-Ahmednagar railway line via Kalyan was also in planning stage with survey of this project carried out on 1970, 2000, 2014 etc. # Change the connection mode back to git.Indian Railways and Mumbai Suburban Railway stationĬhhatrapati Shivaji Maharaj Terminus Area, Fort, Mumbai, Maharashtra 400001ġ8★6′23″N 72★0′08″E / 18.9398°N 72.8355☎ / 18.9398 72.8355 Remember to grab the password, or use drush uli later.ĭrush -y si -strict=0 -site-name="$site_description" profile-nameĭrush psite-commit $site_uuid dev -message="Installed Drupal with profile-name." # We need -strict=0 because Pantheon's drush alias files don't work with Drush # Download Drush makefile and use it to build the site on Pantheon dev Ssh-keyscan -p 2222 -t rsa,dsa v.$site_ 2>&1 | sort -u - ~/.ssh/known_hosts > ~/.ssh/tmp_hosts Ssh-keyscan -p 2222 -t rsa,dsa v.$site_ 2>&1 | sort -u - ~/.ssh/known_hosts > ~/.ssh/tmp_hostsĬat ~/.ssh/tmp_hosts > ~/.ssh/known_hosts # TODO: Clean this up so we only sort once # to continue connecting (yes/no)?' later # Add code and dev servers to known_hosts so we don't get 'Are you sure you wish # Change the connection mode on the dev environment to SFTP. # Determine the site_uuid of the newly created site. # Create the site on Pantheon using Pantheon's drops-7 upstream as the baseĭrush psite-create $sitename -label="$site_description" -product=21e1fada-199c-492b-97bd-0b36b53a9da0 # Get user input for site specifics and Pantheon credentialsĮcho "Enter your Pantheon username (usually your email address):"ĭrush pauth $pantheon_user -password=$pantheon_password Comments or suggestions for improvement are welcome! Since I’m storing the keys mere moments after the servers are created I’m not too worried, but if you’re especially paranoid you might opt for a different solution. I’m not independently verifying these keys before adding them, so the script theoretically is vulnerable to man-in-the-middle attacks. Second, I’m adding keys for the Pantheon appserver and codeserver to my known_hosts file, in order to prevent a couple of annoying “Are you sure you want to continue connecting (yes/no)?” prompts. First, the Drush alias files that Pantheon generates don’t work with Drush 6.0 yet, so I’ve added –strict=0 to all the Drush commands that use aliases. There are two major items of note in the script. When you return, you should have a site at, and a local clone of the site code at. Then answer four questions (the sitename, site description, and your Pantheon login and password), then go out for your beverage of choice. Just cd to the main sites directory on your local machine and run the script (don’t forget to chmod +x after you download, and customize the script with the URL of your makefile and the name of your install profile). Using the script is very straightforward. It still requires that the person creating the site have Drush (and the Terminus Drush extension) installed locally, on a *nix-like machine, but I have visions of a site builder (or even a project manager or account manager) soon being able to provision a new site simply by filling out a form on our Intranet. The shellscript below is derived from example commands included in the Terminus readme. The recent introduction of Pantheon’s Terminus CLI has us well on the way to a much more elegant, automatable solution. So I developed a kludgy workaround involving Drush make and importing the resulting tarball through the Pantheon dashboard. Custom start states are available as part of the Pantheon One (formerly Zeus) package, but most of our clients don’t have pockets that deep. The biggest pain point we’ve had was with the initial site provisioning, since we develop most of our sites using a custom install profile, 4Site Hub. Even if a client site doesn’t end up being hosted there for whatever reason, we’ll probably still develop the site on Pantheon because their development tools fit very nicely into our small team’s workflow. ![]() We’re big fans of Pantheon here at 4Site Studios. ![]() Building a site with a custom Drupal install profile using Pantheon and Terminus
0 Comments
Leave a Reply. |