Based on the brainsum/damo-project composer project.
After drush si:
drush urol administrator admin
If using apache add this:
RequestHeader set X-Forwarded-Proto "https"
RequestHeader set X-Forwarded-Port 443
Composer template to kickstart Digital Assets Management projects.
This template was based on the following:
Note: These commands have been tested on linux (ubuntu), they might need changes to work on other systems.
For the latest release:
composer create-project brainsum/damo-project my-damo-project
For a specific release:
composer create-project brainsum/damo-project:0.1.0 my-damo-project
For the latest release:
DAMO_PROJECT_DIR=my-damo-project; mkdir "${DAMO_PROJECT_DIR}" && docker run --rm -u "$(id -u)":"$(id -g)" -w /app --mount type=bind,src="$(pwd)"/"${DAMO_PROJECT_DIR}",dst=/app wodby/drupal-php:7.3-dev-4.14.3 composer create-project brainsum/damo-project .
For a specific release:
DAMO_PROJECT_DIR=my-damo-project; mkdir "${DAMO_PROJECT_DIR}" && docker run --rm -u "$(id -u)":"$(id -g)" -w /app --mount type=bind,src="$(pwd)"/"${DAMO_PROJECT_DIR}",dst=/app wodby/drupal-php:7.3-dev-4.14.3 composer create-project brainsum/damo-project:0.1.0 .
Note: The wodby/drupal-php image is just an example.
Note: Using an image with the hirak/prestissimo
composer package will speed up the process, although it also might break things (see: drupal-composer/drupal-scaffold#101).
If you want to use docker-compose for development, you should copy example.env
as .env
, e.g cp example.env .env
. Update its contents as required.
For starting and stopping the environment you can use the helper scripts provided with the project (startup.sh
and shutdown.sh
). These also look for a docker-compose.local.yml
file so you can version control a generic config file and do local overrides (e.g ports, mounts).
Copy drush/example.drush.yml
as drush/drush.yml
. Update its contents as required.
E.g on linux, you must fix file and directory permissions as well, e.g for "private_files", "web/sites/default/files", "tmp", ...
Use drush site-install --account-pass=somestrongpass --site-mail=mail@currentsite.com --site-name=DAMo damo -y
You also might want to add --account-name
and --account-mail
.
Upload your assets and that's it. You can download them, images can be styled for social media purposes, logo can be added, etc.
The JSON:API module has been enabled, so you can serve your assets through that. An example would be using the FileField Sources JSON API module that allows you to configure file fields to allow downloading files from DAMo directly via the API.
For development info see the DEVELOPMENT.md file.