Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

 

Spinning Up Sites

We are now set up for domination with Pantheon One. Take heed of the new differences:

  1. Create a site within the Kalamuna organization
  2. URLS will now be suffixed in the following form *.at.kalamuna.com as opposed to *.getpantheon.com
  3. Currently use Panopoly as your starting distribution and upstream.
    1. In the future, we'll use HotSauce! as our start state. This is linked to our new canonical upstream: https://github.com/kalamuna/drops-7 which is basically just an out-of-date Panopoly plus Kalatheme 3.x at this point. Eventually this will turn into a magical distro.

 

Useful Tips

Contributing to Pantheon One upstream repos

Hotsauce

  1. If you have a patch that you think should be rolled in: OPEN AN ISSUE HERE https://drupal.org/project/hotsauce
  2. If you have a feature/app that you think should be rolled in: OPEN AN ISSUE HERE https://drupal.org/project/hotsauce
  3. If you have a contrib module that you think should be rolled in: OPEN AN ISSUE HERE https://drupal.org/project/hotsauce

 

Shallow clones

We're not talking about Jango Fett's performance. git shallow clones allow application servers and developers to avoid pulling the full history.

Here's how you can try it:

 

  1. Install git 1.9 or later. Check with git --version
  2. When you clone, add the --depth=1 option: git clone --depth=1 <repository>
  3. Everything else about your workflow shouldn't change at all as long as you don't need older history.

Cloning the repository for getpantheon.com (a normal Panopoly/Drupal 7 site) normally takes 2.5 minutes and 62 MiB. A shallow clone takes 1 minute and 29 MiB.

 

Resources

http://hubdrop.io/ - Mirror drupal.org projects on GitHub.

  • No labels