Download the PHP package brainsum/damopen-project without Composer
On this page you can find all versions of the php package brainsum/damopen-project. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download brainsum/damopen-project
More information about brainsum/damopen-project
Files in brainsum/damopen-project
Package damopen-project
Short Description Template for creating DAMopen projects with composer.
License GPL-2.0-or-later
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package damopen-project
DAMopen - Composer template
Composer template to kickstart Digital Assets Management projects.
This template was based on the following:
Structure
app: the actual Drupal folder. This is the only folder mounted into the docker container, installing Drupal, adding dependencies, using drush, etc. should be executed from here.- Note, in a containerized environment this is the only folder that should be available to the image at build time.
- Git root should still be the project root.
docker: contains Dockerfiles and some helpers for building the images
Installation
Note: These commands have been tested on linux (ubuntu), they might need changes to work on other systems.
Native composer
For the latest release:
For a specific release:
Composer in docker
For the latest release:
For a specific release:
This creates the base structure. After the project installed, you need to enter go to the app folder and use composer install.
Note: Drupal released 9.2, but the damopen distro applies a patch that's not compatible with that version. If composer install fails, you can work around this by adding the following to app/composer.json / extra (See: cweagans/composer-patches) and running it again:
Setup
Environment variables
By default, the project depends on some environment variables. See the settings folder.
(Optional) Docker-compose
If you want to use docker-compose for development, you should update .env as needed (e.g. replaceing damopen with your project's name, adding the hash salt, ...).
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).
Drush
Copy app/drush/example.drush.yml as app/drush/drush.yml and update its contents as required.
Filesystem permission fixes
E.g. on linux, you must fix file and directory permissions as well, e.g for "private_files", "web/sites/default/files", "tmp", ...
Additional settings files
app/settings/example contains multiple pre-defined settings files. Copy settings.local.php to settings to bootstrap your local settings, web/sites/default/settings.php automatically includes it, if present. This helps avoid issues with file permissions for the main settings.php.
Install
Use drush site-install --account-pass=somestrongpass [email protected] --site-name=DAMopen damopen -y
You also might want to add --account-name and --account-mail.
Usage
Main site
Upload your assets and that's it. You can download them, images can be styled for social media purposes, logo can be added, etc.
API
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 DAMopen directly via the API.
Development
For development info see the DEVELOPMENT.md file.
