Add a new service / container for a frontend based in Node / React. Looking for the right Docker Image and integrate it in the DDEV net.

Update Drupal core for the last detected issues, present in: https://www.drupal.org/security

Update some info featured in main README file.

Describe the bug
Now the Portainer Container is always started and working, even if the others containers in the network are stopped. The key always is not the best option for the policies. It must to be changed as hotfix.

For the first MVP version of the project, we need a first initial frontend ready-to-go with the Drupal backend and based in ReactJS.
The goal is build up an internal connection between frontend - backend and getting existing nodes from the frontend, showing a basic list of Drupal Nodes from the React side.

Steps:

1. Initial scaffolding for a new frontend based in ReactJS.
2. Enabling of GraphQL server in Drupal backend side, exposing created nodes (10 articles).
3. Configure GraphQL client in frontend and build requests in order to get the Drupal nodes.
4. Show the returned Drupal nodes in a list.
5. Once the connection is made and working, pass the frontend to a Dockerized environment, in a new container / service.

User Story

As developer 
when I want check and testing the basic features of Summer House platform, 
I need an existing connection between frontend and backend for the decoupled model. 

Enable PHP Codestyling libraries and configure basic settings for Drupal, just as in:

    service: appserver
    cmd: "cd /app/backend && vendor/bin/phpcs --standard=Drupal,DrupalPractice --colors --extensions=inc,info,install,module,php,profile,test,theme web/modules/custom web/profiles/st web/themes/custom"
    description: Check code standards.
  phpcbf:
    service: appserver
    cmd: "cd /app/backend && vendor/bin/phpcbf --standard=Drupal,DrupalPractice --colors --extensions=inc,info,install,module,php,profile,test,theme web/modules/custom web/profiles/st web/themes/custom"
    description: Fix code standard violations automatically.

When we're using $ drush si with params from steps inside .ddev/config.yaml, we're installing the standard installation of Drupal, the by-default version. This enable some resources like shortcut module and others, and by now we're merging this profile with our config files doing some weird steps, just like:

 - exec-host: "([ $(ddev drush eval 'print_r(array_keys(\\Drupal::entityTypeManager()->getDefinitions()));' | grep shortcut -c) -gt 0 ] && (ddev drush entity:delete shortcut_set) || (echo 'No shortcut entities were found in your system.'))"
 - exec: "drush pmu shortcut -y"

Just before:

$ drush cim -y"

Trying to align the default installation and the coming configuration values from our existing files. That's weird and add complexity and some points-of-failure to the process. We need something more light for installation, and the solution must be implementing our custom Drupal Installation Profile and then changing when $ drush site-installcomes.

User Story

As developer 
when I'm installing Summer House in my local environment, 
I need a more easy way of charge the related configuration of the platform. 

Download external resources only if it doesn't exist in local environment at the moment of starting.
Avoiding:

    - exec-host: "wget https://raw.githubusercontent.com/drud/ddev-contrib/master/docker-compose-services/portainer/docker-compose.portainer.yaml"

Check first if file exists.

Change the current name for the docroot in Drupal container (web container in the DDEV context) for something more specific: backend insted of the by-default web, because finally several containers will be focused on different web technologies.

User Story

As developer 
when I'm working with Summer House platform, 
I need a more intuitive naming for folders. 

Pass specific URLs to environment variables available in .env custom files.
I mean, instead of (config.yaml):

  pre-start:
    - exec-host: "wget https://raw.githubusercontent.com/drud/ddev-contrib/master/docker-compose-services/portainer/docker-compose.portainer.yaml"

Load URL in .env file.

I'm facing problems connecting frontend and backend, all containers within the DDEV-local network. I'm getting a CORS error when I'm requesting drupal nodes by GraphQL queries.

Can be bypassed using some browser extension, just like: https://addons.mozilla.org/en-US/firefox/addon/access-control-allow-origin/ but it can't be the best soluttion. We need something built-in.

More info: https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS/Errors/CORSMissingAllowOrigin

In order to install some extra tooling like GrumPHP and others, the current PHP version in backend container has to be updated. And the Drupal core version too.

When Portainer runs, after some minutes, the container seems to be stopped, automatically. If you re-run the Docker container, after minutes this will be stopped one more time.
In logs:

2022/06/14 13:27:04 No administrator account was created after 5 min. Shutting down the Portainer instance for security reasons.

Review the start-up process and turn off this option.

Is your feature request related to a problem? Please describe.
In an onboarding context, it is possible for some scripts to execute very severe actions for the host system without explicit confirmation of execution by the user.
This may cause uncalculated damage to the host system, putting other containers / services / data / volumes at risk. Not everyone has a good understanding of the end results that some actions execute.

Describe the solution you'd like
Request user permissions to make changes to the host system when launching project scripts.

User Story

As user/developer 
When I'm executing some scripts, 
I need to be informed in the best possible way of the actions that some scripts will perform
In order to prevent unforeseen changes to my environment.

Describe the bug
There is an error in prompt when ddev is running, due to a previous existence of the mkdocs folder filled with content from the Summer House Wikipedia. The git clone can't be executed and this launch a warning message. So we have to re-think what we can do in ddev start, if is better delete folder / clear and re-get all the mkdocs contents, being always the most updated version of the internal documentation for the mkdocs container.

To Reproduce
Steps to reproduce the behavior:

1. $ git clone [email protected]:davidjguru/summerhouse.git
2. $ cd summerhouse
3. summerhouse$ ddev start
4. summerhouse$ ddev stop
5. summerhouse$ ddev start

Expected behavior
Check if mkdocs folder already exists and if is available, just delete content and get a new updated copy of the Summer House wiki content from its related repository.

Screenshots

summerhouse$ ddev start
  Starting summerhouse... 
  A portainer service file has been located in your system.
  A frontend react service file has been located in your system.
  A MkDocs service file has been located in your system.
  fatal: destination path './mkdocs/docs' already exists and is not an empty directory.
  Task failed: Exec command '(git clone https://github.com/davidjguru/summerhouse.wiki.git ./mkdocs/docs)' on the host (sankara): exit status 128 

Enable enhanced rendering of data transferred from the backend applying styles, layout and visual order, showing more data (images, author, etc).

Describe the bug
When you're running ddev startyour facing a pair of possible scenarios:

• First installation from zero.
• Just a single restarting / start in your system.

Right now, both processes are sharing the same steps for the backend_drupal container, for instance running composer install but this can execute changes in your system, altering values and running unnecessary steps if you're only starting up the platform. composer install has not to be executed in every ddev start.

Expected behavior
There must be a separation of processes from the use of ddev start, splitting scenarios from a whole install to a single start/restart.
If the dependencies already exist and are installed (vendor, drupal contrib, etc) composer install will not be executed.

Pass info to README File when update code, adding features or new changes.
Working branch: SH-RDM.

For the first MVP version of the project, different actions have been assumed to be executed directly as DDEV-hooks, actions hosted in the /.ddev/config.yaml file.

Steps like:

# Resolve all dependencies by Composer in container.
- composer: install 
# Install Drupal after start if not installed already.
- exec: "(drush status bootstrap | grep -q Successful) || (drush site-install --site-name=SummerHouse --account-name=admin --account-pass=admin --db-url=mysql://db:db@db/db -y && drush user-add-role 'administrator' admin)"
- exec: "drush cr"

This can be confusing and messy when it comes to the initial configuration of the project and its deployment. We need to separate responsibilities, define scope at each step and distribute the initial installation/deployment tasks between the following tooling parts:

1. Composer scripting: pre-install-cmd, pre-update-cmd, post-install-cmd, post-update-cmd.
2. DDEV Hooks: pre-start, post-start, pre-stop, pre-composer, post-composer, etc.
3. DDEV custom commands: .ddev/commands/host, .ddev/commands/<container>, .ddev/commands/.

User Story

As developer 
when I want extend the project Summer House with new features related to config/deploy/build up, 
I need a more intuitive and rational organization in order to understand how + where can I do my changes. 

Prepare an external data loading in backend_drupal, implementing a new custom entity type.

Describe the bug
When creating the Docker container for service frontend_react the script start.sh is running as root user and then the folder /summerhouse/frontend_react/node_modules/ can't be deleted by other scripts and requires sudo for instructions.

Enable testing for React components using Jest.

In order to prepare the basic installation scenario, Summer House require a basic script for installing the resources: Git, Docker, Docker-Compose, DDEV and some packages like wget and related.

Goal: provide a basic script for install basic resources and preparing the scenario for the Summer House Installation.

As developer 
when I want check the project, 
I need a fast tool for install the basic resources in my Linux distro. 

Move Drupal core in SummerHouse to 10.x version.

Describe the bug
When you're using versions of DDEV under 1.18 you're facing problems in some installation steps due to non-recognition of special characters, for instance when execute:

- exec-host: "([ $(ddev drush eval 'print_r(array_keys(\\Drupal::entityTypeManager()->getDefinitions()));'

Present in hook pre-start described in config.yml file for DDEV setup. This leads to installation errors and various command execution problems. As the command is not executed correctly, it does not delete the shortcuts and therefore also crashes when importing the configuration.

To Reproduce
Steps to reproduce the behavior:

1. Use DDEV under 1.19 version.
2. Run ddev start after git clone ..., etc.
3. See errors from prompt.

Expected behavior
Download, configure and install all the setup for Summer House as in 1.19 or above versions of DDEV.

Additional context
Related:
ddev/ddev#2547 (comment)
ddev/ddev#1648 (comment)

For now the frontend area created with React remains "by-default", with no changes, fixes or layout/styles modifications.
So it is necessary to create a minimal articulation to present the React frontend of the platform: a new layout with ad-hoc styles.

MkDocs is a static site generator for project documentations, it build up a live - wiki from browser using markdown files as source.
It can be interesting add a new specific container for Summer House deploying MkDocs in order to make the platform more self-contained. The markdown source files can be taken from the Github Wiki and then converted to a website pages.

User Story

As developer 
when I'm installing Summer House in my local environment, 
I need the project to be as self-contained as possible to facilitate my installation and learning process. 

Now the config related files are not being re-usable since we're building a new settings file in every start-up from DDEV, with differentes hashcode for identification. So, the site is different every time we load it. We need a persistent storage for a central settings file and using it always with the same ID. We need folders + scripting + composer + DDEV all in the game.

Goal: Build a mixin' of composer install script + local folder with reusable resources.

As developer 
when I want install the project in a local environment, 
I need a load of the default configuration files, aligned with the hash ID of the site.

Errors running phpcs in Github Actions.

Run cd ci
  cd ci
  vendor/bin/phpcs
  shell: /usr/bin/bash -e {0}
ERROR: Referenced sniff "SlevomatCodingStandard.ControlStructures.RequireNullCoalesceOperator" does not exist

In: https://github.com/davidjguru/summerhouse/actions/runs/2623662436

Related:
https://jet.dev/blog/coding-standards-phpcs-drupal-github-actions/
https://www.drupal.org/project/coder/issues/3262291
https://gorannikolovski.com/blog/referenced-sniff-slevomat-coding-standard-does-not-exist