Skip to content

Instantly share code, notes, and snippets.

@dergachev

dergachev/vagrant-drupal-repo-structure.md

Last active December 19, 2015 01:39
Show Gist options
  • Save dergachev/5877262 to your computer and use it in GitHub Desktop.
Save dergachev/5877262 to your computer and use it in GitHub Desktop.
Download ZIP

Revisions

  1. dergachev revised this gist Jun 27, 2013. 1 changed file with 6 additions and 2 deletions.
    8 changes: 6 additions & 2 deletions vagrant-drupal-repo-structure.md
    View file
    Original file line number Diff line number Diff line change
    @@ -30,8 +30,7 @@ another as a git submodule.

    ## Idea 2: Berksfile and Vagrantfile are added to project root.

    The vagrant root directory would look like this (assuming a specific directory structure of
    Drupal projects):
    The project structure is as follows:

    - site
    - index.php
    @@ -44,3 +43,8 @@ Drupal projects):
    The copy command would be as follows

    cp -R /vagrant /var/shared/sites/cooked.drupal

    This requires exposing a chef attribute for VHOST_ROOT, which is where apache would serve from.
    In this case, it would be '/var/shared/sites/cooked.drupal/site'.

    Keep in mind that we don't want to hardcode /vagrant anywhere in the cookbook.
  2. dergachev revised this gist Jun 27, 2013. 1 changed file with 17 additions and 14 deletions.
    31 changes: 17 additions & 14 deletions vagrant-drupal-repo-structure.md
    View file
    Original file line number Diff line number Diff line change
    @@ -2,18 +2,13 @@

    We're exploring alternative layouts for the vagrant-drupal repo structure.

    ## Idea 1: project subdirectory
    ## Idea 1: project sub-repo

    Assuming we want to keep Vagrantfile and Berksfile in git, and assuming
    that we have an existing Drupal project repo, the layout will be as follows:

    cp /vagrant/project DEPLOY_DIR

    In this case there needs to be another attribute pointing to Drupal
    root in deployment directory (or equivalently in the [project] folder).
    if you decide to keep the Vagrantfile in your Drupal
    project repo, all your drupal projects will look like:

    - Project
    - project
    - site
    - db
    - scripts
    @@ -22,16 +17,20 @@ project repo, all your drupal projects will look like:
    - Vagrantfile
    - .git

    The copy command will look as follows:

    cp -R /vagrant/project /var/shared/sites/cooked.drupal

    In this case there needs to be another attribute pointing to Drupal
    root in deployment directory (or equivalently in the [project] folder).

    This is problematic because Vagrantfile and Berksfile cannot be added to the project repo
    without creating a new repo merging the two `.git`s, or adding one to
    another as a git submodule.

    ## IDEA-2 : Berksfile and Vagrantfile are added to project root.

    cp -R /vagrant DEPLOY_DIR
    ## Idea 2: Berksfile and Vagrantfile are added to project root.

    The vagrant root directory
    would look like this (assuming a specific directory structure of
    The vagrant root directory would look like this (assuming a specific directory structure of
    Drupal projects):

    - site
    @@ -41,3 +40,7 @@ Drupal projects):
    - Vagrantfile
    - Berksfile
    - .git

    The copy command would be as follows

    cp -R /vagrant /var/shared/sites/cooked.drupal
  3. dergachev renamed this gist Jun 27, 2013. 1 changed file with 5 additions and 1 deletion.
    6 changes: 5 additions & 1 deletion vagrant-drupal-workflow.md → vagrant-drupal-repo-structure.md
    View file
    Original file line number Diff line number Diff line change
    @@ -1,6 +1,10 @@
    # vagrant-drupal repo structure

    ## IDEA-1 : project subdirectory/subrepository?
    We're exploring alternative layouts for the vagrant-drupal repo structure.

    ## Idea 1: project subdirectory


    cp /vagrant/project DEPLOY_DIR

  4. dergachev revised this gist Jun 27, 2013. 1 changed file with 1 addition and 1 deletion.
    2 changes: 1 addition & 1 deletion vagrant-drupal-workflow.md
    View file
    Original file line number Diff line number Diff line change
    @@ -1,4 +1,4 @@
    # Project repo structure for vagrant-drupal
    # vagrant-drupal repo structure

    ## IDEA-1 : project subdirectory/subrepository?
  5. dergachev revised this gist Jun 27, 2013. 1 changed file with 15 additions and 15 deletions.
    30 changes: 15 additions & 15 deletions vagrant-drupal-workflow.md
    View file
    Original file line number Diff line number Diff line change
    @@ -9,14 +9,14 @@ root in deployment directory (or equivalently in the [project] folder).
    if you decide to keep the Vagrantfile in your Drupal
    project repo, all your drupal projects will look like:

    - Project
    - site
    - db
    - scripts
    - .git
    - Berksfile
    - Vagrantfile
    - .git
    - Project
    - site
    - db
    - scripts
    - .git
    - Berksfile
    - Vagrantfile
    - .git

    This is problematic because Vagrantfile and Berksfile cannot be added to the project repo
    without creating a new repo merging the two `.git`s, or adding one to
    @@ -30,10 +30,10 @@ The vagrant root directory
    would look like this (assuming a specific directory structure of
    Drupal projects):

    - site
    - index.php
    - db
    - scripts
    - Vagrantfile
    - Berksfile
    - .git
    - site
    - index.php
    - db
    - scripts
    - Vagrantfile
    - Berksfile
    - .git
  6. dergachev revised this gist Jun 27, 2013. 1 changed file with 4 additions and 3 deletions.
    7 changes: 4 additions & 3 deletions vagrant-drupal-workflow.md
    View file
    Original file line number Diff line number Diff line change
    @@ -1,4 +1,4 @@
    # Drupal project repository structure for vagrant-drupal
    # Project repo structure for vagrant-drupal

    ## IDEA-1 : project subdirectory/subrepository?
    @@ -24,8 +24,9 @@ another as a git submodule.

    ## IDEA-2 : Berksfile and Vagrantfile are added to project root.

    In this case, we
    copy `/vagrant/.` to deployment directory. The vagrant root directory
    cp -R /vagrant DEPLOY_DIR

    The vagrant root directory
    would look like this (assuming a specific directory structure of
    Drupal projects):

  7. dergachev revised this gist Jun 27, 2013. 1 changed file with 38 additions and 27 deletions.
    65 changes: 38 additions & 27 deletions vagrant-drupal-workflow.md
    View file
    Original file line number Diff line number Diff line change
    @@ -1,27 +1,38 @@
    - idea 1 : project subdirectory/subrepository? cp /vagrant/project deployment directory.
    in this case there needs to be another attribute pointing to Drupal
    root in deployment directory (or equivalently in the [project] folder).
    if you decide to keep the Vagrantfile in your Drupal
    project repo, all your drupal projects will look like:
    - Project
    - site
    - db
    - scripts
    - .git
    - Berksfile
    - Vagrantfile
    - .git
    And this is problematic because Vagrantfile and Berksfile cannot be added to the project repo
    without creating a new repo merging the two `.git`s, or adding one to
    another as a git submodule.
    - idea 2 : Berksfile and Vagrantfile are added to project root. In this case, we
    copy `/vagrant/.` to deployment directory. The vagrant root directory
    would look like this (assuming a specific directory structure of
    Drupal projects):
    - site
    - index.php
    - db
    - scripts
    - .git
    - Vagrantfile
    - Berksfile
    # Drupal project repository structure for vagrant-drupal

    ## IDEA-1 : project subdirectory/subrepository?
    cp /vagrant/project DEPLOY_DIR

    In this case there needs to be another attribute pointing to Drupal
    root in deployment directory (or equivalently in the [project] folder).
    if you decide to keep the Vagrantfile in your Drupal
    project repo, all your drupal projects will look like:

    - Project
    - site
    - db
    - scripts
    - .git
    - Berksfile
    - Vagrantfile
    - .git

    This is problematic because Vagrantfile and Berksfile cannot be added to the project repo
    without creating a new repo merging the two `.git`s, or adding one to
    another as a git submodule.

    ## IDEA-2 : Berksfile and Vagrantfile are added to project root.

    In this case, we
    copy `/vagrant/.` to deployment directory. The vagrant root directory
    would look like this (assuming a specific directory structure of
    Drupal projects):

    - site
    - index.php
    - db
    - scripts
    - Vagrantfile
    - Berksfile
    - .git
  8. @amirkdv amirkdv created this gist Jun 27, 2013.
    27 changes: 27 additions & 0 deletions vagrant-drupal-workflow.md
    View file
    Original file line number Diff line number Diff line change
    @@ -0,0 +1,27 @@
    - idea 1 : project subdirectory/subrepository? cp /vagrant/project deployment directory.
    in this case there needs to be another attribute pointing to Drupal
    root in deployment directory (or equivalently in the [project] folder).
    if you decide to keep the Vagrantfile in your Drupal
    project repo, all your drupal projects will look like:
    - Project
    - site
    - db
    - scripts
    - .git
    - Berksfile
    - Vagrantfile
    - .git
    And this is problematic because Vagrantfile and Berksfile cannot be added to the project repo
    without creating a new repo merging the two `.git`s, or adding one to
    another as a git submodule.
    - idea 2 : Berksfile and Vagrantfile are added to project root. In this case, we
    copy `/vagrant/.` to deployment directory. The vagrant root directory
    would look like this (assuming a specific directory structure of
    Drupal projects):
    - site
    - index.php
    - db
    - scripts
    - .git
    - Vagrantfile
    - Berksfile