Dru.io

Drupal repository Dru.io community

Navigation by repository:

• Issues - questions, improvement proposals, requests, discussion. Here there is a discussion of the technical side of the project.
• List of changes in the community - TODO.
• API - API for the site of the community.

Table of contents

• Description
• Creating a local copy of the resource
  • Pure copy of the resource
• Design source

Description

This repository contains a code base for the Drupal site Dru.io. Thanks to this, everyone can look into the sources, see how everything is arranged and done, help with the finalization or development of new functionality, correct errors, etc. Or just assemble yourself a similar site from scratch.

At the moment, the database is not ready, but the module is already ready for an adjacent project, and as soon as everything is closer to launch, the database, as for Drupal 7 versions, will be publicly available. At the moment, it makes no sense, since it simply does not exist.

Creating a local copy of the resource

Pure copy of the resource

Thanks to the configurations in Drupal 8, we can make an absolute copy of the resource, from scratch, without any traces of the main site. Yes, you can make an absolutely identical site, without users, content, etc., with all current functionality and expand your own community on this. It is enough to suffer the repository and follow the steps:

1. First of all, you need to encourage the repository in the root folder of your web server where you want to deploy a copy of the resource. To be guided in the current folder, just write: git clone -b 8.x https://github.com/dru-io/Dru.io.git .
2. Further, it is necessary to establish all the dependencies, they include: the Drupal core, all Contrible modules, profiles and topics that are used on the resource, as well as all Vendor libraries. To do this, we use Composer. The repository has composer.json , which contains all the necessary dependencies, just install them: composer install .
3. We go to the site (Localhost, Example.com), depending on where and how they were deployed. On the page, the installation of the new Drupal website will open. This is the right behavior.
4. The easiest and fastest way is to launch the installation via Drush, drush site-install --verbose config_installer config_installer_sync_configure_form.sync_directory=../config/sync --yes . If you start through the browser: start the Drupal installation as usual, only by step the profile you need to choose a config Installer profile. In the proposed settings at the next step, just agree to agree, since the configurations have already been loaded with the repository and Config Installer will find them himself.
5. We are waiting for the end of the installation, rejoice.
6. For the correct operation of the topic, you also need to go to the folder with the theme of cd web/themes/custom/druio_theme and set the dependences of yarn install .

If there are any questions about installing (some standard Docker-images have seen the nuances from 200 Ajax-error during installation), create Issue here https://github.com/dru-io/dru.io/issues or contact the general telegram chat https://t.me/dripal_ruus , always glad to tell.

You can set any settings during the installation. It is held as on a clean site. There will be absolutely no problems with this. You can give the site any name, indicate the USERNAME and Password, in general, everything you want. After installation, you will have a completely clean and ready to use clone dru.io.