You are here

README.txt in Git Deploy 6

Same filename and directory in other branches
  1. 8.2 README.txt
  2. 6.2 README.txt
  3. 7.2 README.txt
  4. 7 README.txt
INTRODUCTION
------------

Git Deploy lets you develop on a live site and still satisfy version
requirements and get accurate results from the update status system. This makes
it easier to contribute to the projects you use.

Version information is added automatically when the Drupal packaging system
creates a release. If you check out a contributed project from the Drupal
repository with Git, it should not have any version information. Git Deploy gets
the missing version information from the project's Git log.

* Project page: https://www.drupal.org/project/git_deploy
* Issue queue: https://www.drupal.org/project/issues/git_deploy


REQUIREMENTS
------------

* glip. Git Deploy is tested against version 1.1, available at
  https://github.com/halstead/glip/tree/1.1. All updates to glip are tracked on
  GitHub. glip is licensed under GPLv2.
* To get accurate update status information, enable the myDropWizard module
  (https://www.drupal.org/project/mydropwizard).


INSTALLATION
------------

1. Download the Zip file from https://github.com/halstead/glip/zipball/1.1, or
   run these Git commands:

   git clone git://github.com/halstead/glip.git
   cd glip
   git checkout 1.1

2. Place the glip directory at sites/all/libraries/glip so that you have
   sites/all/libraries/glip/lib.


ALTERNATIVES
------------

A project’s dev release changes whenever a maintainer updates its branch. To
enforce consistency among sites using a dev release, you can lock them to the
same release by checking out a specific Git commit. You would not contribute
changes from these sites back to the project. Drush 8
(https://docs.drush.org/en/8.x/) can automatically add version information to
projects you check out with Git.

* The drush pm-download command with options --package-handler=git_drupalorg
  --gitinfofile performs a Git clone and checkout and adds version information
  to the project info file.
* The drush make command automatically adds version information to the project
  info file without additional options.

Composer Deploy (https://www.drupal.org/project/composer_deploy) gets version
information from Composer metadata for projects installed with Composer.

File

README.txt
View source
  1. INTRODUCTION
  2. ------------
  3. Git Deploy lets you develop on a live site and still satisfy version
  4. requirements and get accurate results from the update status system. This makes
  5. it easier to contribute to the projects you use.
  6. Version information is added automatically when the Drupal packaging system
  7. creates a release. If you check out a contributed project from the Drupal
  8. repository with Git, it should not have any version information. Git Deploy gets
  9. the missing version information from the project's Git log.
  10. * Project page: https://www.drupal.org/project/git_deploy
  11. * Issue queue: https://www.drupal.org/project/issues/git_deploy
  12. REQUIREMENTS
  13. ------------
  14. * glip. Git Deploy is tested against version 1.1, available at
  15. https://github.com/halstead/glip/tree/1.1. All updates to glip are tracked on
  16. GitHub. glip is licensed under GPLv2.
  17. * To get accurate update status information, enable the myDropWizard module
  18. (https://www.drupal.org/project/mydropwizard).
  19. INSTALLATION
  20. ------------
  21. 1. Download the Zip file from https://github.com/halstead/glip/zipball/1.1, or
  22. run these Git commands:
  23. git clone git://github.com/halstead/glip.git
  24. cd glip
  25. git checkout 1.1
  26. 2. Place the glip directory at sites/all/libraries/glip so that you have
  27. sites/all/libraries/glip/lib.
  28. ALTERNATIVES
  29. ------------
  30. A project’s dev release changes whenever a maintainer updates its branch. To
  31. enforce consistency among sites using a dev release, you can lock them to the
  32. same release by checking out a specific Git commit. You would not contribute
  33. changes from these sites back to the project. Drush 8
  34. (https://docs.drush.org/en/8.x/) can automatically add version information to
  35. projects you check out with Git.
  36. * The drush pm-download command with options --package-handler=git_drupalorg
  37. --gitinfofile performs a Git clone and checkout and adds version information
  38. to the project info file.
  39. * The drush make command automatically adds version information to the project
  40. info file without additional options.
  41. Composer Deploy (https://www.drupal.org/project/composer_deploy) gets version
  42. information from Composer metadata for projects installed with Composer.