EDIT

# CDM Data Portal

Drupal 7 modules and themes as web frontend to publish data hosted in a [cdm server](https://github.com/cybertaxonomy/cdm-server).

Dependencies of sub-projects like *modules/cdm_dataportal*, *themes/zen_dataportal*, etc still have manually copied dependencies. 

## Project structure

* `./modules`: drupal modules, the actual **cdm_dataportal** module is found here. 

* `./scripts/jenkins-ci`: scripts for testing, release, deployment in jenkins.

* `./src`: java project with selenium tests

* `./themes`: drupal themes

**Generated folders which must not be comitted to the repository:**

* `./target`: target folder of maven, used for the side documentation (source in `./site`) and selenium tests (source in `./src`)

* `./screenshots`: screenshots taken during the selenium test execution

* `./vendor`: composer cache

* `./web`: final installation bundle of drupal 7 with modules, themes, profiles, etc. that is created by `composer update`

**Creation of the composer project**

The parent composer project (`./composer.json`) has been created using the official drupal project template:

~~~

composer create-project drupal-composer/drupal-project:7.x-dev -n dist

~~~

### On using composer with drupal projects

https://www.drupal.org/docs/develop/using-composer/using-composer-to-install-drupal-and-manage-dependencies

https://www.drupal.org/docs/develop/using-composer/using-composer-with-drupal

https://www.drupal.org/docs/develop/using-composer/managing-dependencies-for-a-custom-project

to: https://cybertaxonomy.eu/dataportal/installation

to install the cdm-dataportal Drupal 7 project e.g.

~~~

cd /var/www

cdm-dataportal module, zen_dataportal theme and other requirements. The drupal-7 installation is in the sub folder `./web`

~~~

and to activate one of them, preferably the ssl site configuration:

~~~

sudo cp drupal-7-cdm-dataportal/scripts/apache2.4/dataportal.test* /etc/apache2/sites-available/

sudo systemctl restart apache2

Make an executable copy from `new-site.sh.template` as `new-site.sh` 

~~~

~~~

## Configure below variables

SITE_NAME='test-site'

# HOST_NAME and PROTOCOL determine the base URL of the new site

# The default values will form the base URL like http://dataportal.test

# See also MULTI_SITE below

HOST_NAME='dataportal.test'

PROTOCOL='https' # values 'http' ot https'

# For MULTI_SITE=0 the site will be installed at the base BASE_URL

# In multisite setups (MULTI_SITE=1), however, the site URL results 

# in http://dataportal.test/test-site

# !! Mutisite support ist still experimental !!

MULTI_SITE=0 # values: 1 = true, 0 or other = false

ADMIN_PWD='change--me'

ADMIN_EMAIL='admin@dataportal.test'

MYSQL_PWD='change--me'

DB_PREFIX='drupal7_dataportal_'

~~~

installation by the content of the installation package.

* Pro: Few simple steps.

~~~

cd /var/www

mv drupal-7-cdm-dataportal drupal-7-cdm-dataportal.last

~~~

remove old installation packages

~~~

now follow the steps in the chapter **Download & extract** above.

finally copy the default site to the new installation 

~~~

cp -r drupal-7-cdm-dataportal.last/web/sites/default/ drupal-7-cdm-dataportal/web/sites/

~~~

~~~

drush updatedb

drush cc all

~~~

~~~

rm -r drupal-7-cdm-dataportal.last

~~~

#### Preparation

directory `/var/www/drupal-7-cdm-dataportal`. In the following we assume you have installed composer this way and 

will use `./composer` instead of `composer`.

php -r "copy('https://getcomposer.org/installer', 'composer-setup.php');"

php -r "if (hash_file('sha384', 'composer-setup.php') === '756890a4488ce9024fc62c56153228907f1545c228516cbf63f885e036d37e9a59d27d63f46af1d4d07ee0f76181c7d3') { echo 'Installer verified'; } else { echo 'Installer corrupt'; unlink('composer-setup.php'); } echo PHP_EOL;"

php composer-setup.php --filename=composer --version 1.10.22

php -r "unlink('composer-setup.php');"

dataportal-module it is highly recommended to un-shallow the git repository clone

~~~

git fetch --unshallow

git config remote.origin.fetch "+refs/heads/*:refs/remotes/origin/*"

git fetch origin

git checkout origin/master

~~~

This will also install **drush**

~~~

 ./composer install --no-dev

~~~

Hence, updating the dataportal only involves checking out the according release from the git remote:

To see the list of available release tags:

~~~

git tag --list | egrep '[0-9]+\.[0-9]+\.[0-9]+' | sort -V

~~~

~~~

https://dataportal.test. Please adapt to your specific settings if needed.

~~~

./vendor/drush/drush/drush -r /var/www/drupal-7-cdm-dataportal/web/ -l https://dataportal.test cc all

It will 

1. create backups

1. set the site(s) to maintenance mode   

1. Update drupal core and contributed modules via `composer`

1. Run any pending database updates and clear the caches

A brief help for this script is available from `scripts/admin/update-dependencies.sh --help` 

~~~

  --deactivate-install :  The install.php will be hidden by appending '.off' to the filename

  -h, --help:  Print this help text

  --mailto <ADDRESS>:  send a email to the ADDRESS with a log of the update process

  --multi-site:  Do a multi-site update. Requires dataportals-drush. 

        See https://dev.e-taxonomy.eu/svn/trunk/server-scripts/dataportal-admin/

  --site-url:  The site url to be used with drush. This option disables the --multi-site option

Update a single site installation with default site URL

~~~

~~~

~~~

Update a multi-site installation with custom site URL

~~~

scripts/admin/update-dependencies.sh --deactivate-install --multi-site