Drupal.cz community website

Chat:

Build status

Branch	Build status
Master
Develop

Contents

• acquia-utils/ - Acquia cloud specific tools.
• config/ - Exported Drupal configutation.
• docroot/ - Website directory.
• hooks/ - Acquia cloud hooks. (See https://docs.acquia.com/cloud/manage/cloud-hooks )
• library/ - Acquia cloud libraries.
• tests/ - Collection of tests for Travis CI and local development.
• .gitignore - Gitignore.
• .travis.yml - Travis CI test suite configuration.
• scrub.sql - script to strip sensitive data from D6 production database.
• slim.sql - script to make scrubbed database smaller so we can run tests quicker.

Requirements

• Install composer: https://getcomposer.org/doc/00-intro.md
• Install Drush version 8: http://docs.drush.org/en/master/install/

Getting the site up and running.

• Get your copy of the code:
  • Fork this repository. ( https://help.github.com/articles/fork-a-repo/ )
  • Clone your repository.
  • git clone [email protected]:[YOUR-NAME]/drupalcz.git drupalcz
  • cd drupalcz
• Prepare your database and fill the credentials into your new local config.
  • cp docroot/sites/default/default.settings.local.php docroot/sites/default/settings.local.php
  • edit this config: docroot/sites/default/settings.local.php
• Install the site (it will use the Drupal.cz distribution).
  • cd docroot
  • drush si
  • Import configuration:
  • drush cim -y
  • Login to new site:
  • drush uli
• Optional: Migrate data from D6 Drupal.cz
  • Get the database snapshot: https://github.com/Drupalcz/drupalcz_db
  • Import it into new database separarate from D8 version.
  • See docroot/sites/default/default.settings.local.php for info how to connect second DB.
  • Enable module with migration definitions:
  • drush en dcz_migrate -y
  • See which migrations are available:
  • drush migrate-status
  • Run the migration:
  • drush migrate-import --group=dcz6 -vvv
  • Check results:
  • drush migrate-status

Contributing

• We are using GitFlow(https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow/) branching strategy
  • you need to create feature/NAME branch for each issue
  • after you finish work on issue, create pull request against develop branch
• Commit your changes. ( http://chris.beams.io/posts/git-commit/ )
• Create pull request. https://help.github.com/articles/creating-a-pull-request/