documentació https://planet.communia.org/es es Git wiki documentation in native drupal help pages https://planet.communia.org/es/content/git-wiki-documentation-native-drupal-help-pages <!-- THEME DEBUG --> <!-- THEME HOOK: 'field' --> <!-- FILE NAME SUGGESTIONS: * field--node--title--blog--rss.html.twig * field--node--title--blog.html.twig x field--node--title.html.twig * field--node--blog.html.twig * field--title.html.twig * field--string.html.twig * field.html.twig --> <!-- BEGIN OUTPUT from 'themes/contrib/stable/templates/field/field--node--title.html.twig' --> <span>Git wiki documentation in native drupal help pages</span> <!-- END OUTPUT from 'themes/contrib/stable/templates/field/field--node--title.html.twig' --> <!-- THEME DEBUG --> <!-- THEME HOOK: 'field' --> <!-- FILE NAME SUGGESTIONS: * field--node--uid--blog--rss.html.twig * field--node--uid--blog.html.twig x field--node--uid.html.twig * field--node--blog.html.twig * field--uid.html.twig * field--entity-reference.html.twig * field.html.twig --> <!-- BEGIN OUTPUT from 'themes/contrib/stable/templates/field/field--node--uid.html.twig' --> <span> <!-- THEME DEBUG --> <!-- THEME HOOK: 'username' --> <!-- BEGIN OUTPUT from 'themes/custom/planet_foundated/templates/username.html.twig' --> <a href="/user/1" class="visually-hidden p-author h-card" rel="author" title="kinta">kinta <img src="" alt="kinta" /> </a> <a title="View user profile." href="/es/users/kinta">kinta</a> <!-- END OUTPUT from 'themes/custom/planet_foundated/templates/username.html.twig' --> </span> <!-- END OUTPUT from 'themes/contrib/stable/templates/field/field--node--uid.html.twig' --> <!-- THEME DEBUG --> <!-- THEME HOOK: 'field' --> <!-- FILE NAME SUGGESTIONS: * field--node--created--blog--rss.html.twig * field--node--created--blog.html.twig x field--node--created.html.twig * field--node--blog.html.twig * field--created.html.twig * field--created.html.twig * field.html.twig --> <!-- BEGIN OUTPUT from 'themes/contrib/stable/templates/field/field--node--created.html.twig' --> <span> <!-- THEME DEBUG --> <!-- THEME HOOK: 'time' --> <!-- BEGIN OUTPUT from 'themes/contrib/stable/templates/field/time.html.twig' --> <time datetime="2024-02-27T18:03:27+01:00" title="Tuesday, February 27, 2024 - 18:03">Tue, 02/27/2024 - 18:03</time> <!-- END OUTPUT from 'themes/contrib/stable/templates/field/time.html.twig' --> </span> <!-- END OUTPUT from 'themes/contrib/stable/templates/field/field--node--created.html.twig' --> <!-- THEME DEBUG --> <!-- THEME HOOK: 'field' --> <!-- FILE NAME SUGGESTIONS: * field--node--body--blog--rss.html.twig * field--node--body--blog.html.twig * field--node--body.html.twig * field--node--blog.html.twig * field--body.html.twig * field--text-with-summary.html.twig x field.html.twig --> <!-- BEGIN OUTPUT from 'themes/contrib/zurb_foundation/templates/field.html.twig' --> <div class="body field field--node-body field--name-body field--type-text-with-summary field--label-hidden field__item"><p>In last projects, here in communia we are using more and more the gitlab suite tools that are offering many free software projects. Calling projects for their own name: kde with its <a href="https://invent.kde.org">https://invent.kde.org</a> , freedesktop with its <a href="https://gitlab.freedesktop.org">https://gitlab.freedesktop.org</a> , and where we are more active; <a href="https://gitlab.com">https://gitlab.com</a>  and drupalcode.org <a href="https://git.drupalcode.org">https://git.drupalcode.org</a> .</p><p>The schema that we are using is a broader group that includes the drupal recommended project and also where we are including the custom modules, themes, issues, and the wiki documentation. This way we can attach project references to each page, and also the wiki is part of the whole project system.</p><p>We found that when we are providing the project to the group(being a customer, and association or a social project), the content editor or the collaborator is a different person than the one who is reporting issues and has access to gitlab. So this person hasn't access to the forged wiki documentation. Of course that the wiki could be exported to pdf, hosted as mark-down with nextcloud, or served using ruby with gollum. But it will be detached of your final shiny drupal product.</p><p>So here comes this simple module: <a href="https://www.drupal.org/project/git_wiki_help">https://www.drupal.org/project/git_wiki_help</a> . With it, you could add the exported or cloned git wiki to a directory in (private) files path. And then it will be accessible in native drupal administrator help pages, giving the person who administrates the web the general project documentation. </p><p>Take note that wiki is not updated in real-time as if there's an update in git wiki it needs to manually pulled (or If using git you could hang to git hooks to update automatically).</p></div> <!-- END OUTPUT from 'themes/contrib/zurb_foundation/templates/field.html.twig' --> <!-- THEME DEBUG --> <!-- THEME HOOK: 'field' --> <!-- FILE NAME SUGGESTIONS: * field--node--field-tags--blog--rss.html.twig * field--node--field-tags--blog.html.twig * field--node--field-tags.html.twig * field--node--blog.html.twig * field--field-tags.html.twig * field--entity-reference.html.twig x field.html.twig --> <!-- BEGIN OUTPUT from 'themes/contrib/zurb_foundation/templates/field.html.twig' --> <div class="field field--node-field-tags field--name-field-tags field--type-entity-reference field--label-inline clearfix"> <div class="field-label">Tags</div> <div class="field__items"> <div class="field__item"><a href="/ca/etiquetes/drupal" hreflang="ca">Drupal</a></div> <div class="field__item"><a href="/ca/etiquetes/documentacio" hreflang="ca">documentació</a></div> </div> </div> <!-- END OUTPUT from 'themes/contrib/zurb_foundation/templates/field.html.twig' --> <!-- THEME DEBUG --> <!-- THEME HOOK: 'links__node' --> <!-- FILE NAME SUGGESTIONS: * links--node.html.twig * links--node.html.twig x links.html.twig --> <!-- BEGIN OUTPUT from 'themes/custom/planet_foundated/templates/links.html.twig' --> <!-- END OUTPUT from 'themes/custom/planet_foundated/templates/links.html.twig' --> Tue, 27 Feb 2024 17:03:27 +0000 kinta 6570 at https://planet.communia.org https://planet.communia.org/es/content/git-wiki-documentation-native-drupal-help-pages#comments Google Structured Data docs https://planet.communia.org/ca/content/google-structured-data-docs <!-- THEME DEBUG --> <!-- THEME HOOK: 'field' --> <!-- FILE NAME SUGGESTIONS: * field--node--title--link--rss.html.twig * field--node--title--link.html.twig x field--node--title.html.twig * field--node--link.html.twig * field--title.html.twig * field--string.html.twig * field.html.twig --> <!-- BEGIN OUTPUT from 'themes/contrib/stable/templates/field/field--node--title.html.twig' --> <span>Google Structured Data docs</span> <!-- END OUTPUT from 'themes/contrib/stable/templates/field/field--node--title.html.twig' --> <!-- THEME DEBUG --> <!-- THEME HOOK: 'field' --> <!-- FILE NAME SUGGESTIONS: * field--node--uid--link--rss.html.twig * field--node--uid--link.html.twig x field--node--uid.html.twig * field--node--link.html.twig * field--uid.html.twig * field--entity-reference.html.twig * field.html.twig --> <!-- BEGIN OUTPUT from 'themes/contrib/stable/templates/field/field--node--uid.html.twig' --> <span> <!-- THEME DEBUG --> <!-- THEME HOOK: 'username' --> <!-- BEGIN OUTPUT from 'themes/custom/planet_foundated/templates/username.html.twig' --> <a href="/user/1" class="visually-hidden p-author h-card" rel="author" title="kinta">kinta <img src="" alt="kinta" /> </a> <a title="View user profile." href="/es/users/kinta">kinta</a> <!-- END OUTPUT from 'themes/custom/planet_foundated/templates/username.html.twig' --> </span> <!-- END OUTPUT from 'themes/contrib/stable/templates/field/field--node--uid.html.twig' --> <!-- THEME DEBUG --> <!-- THEME HOOK: 'field' --> <!-- FILE NAME SUGGESTIONS: * field--node--created--link--rss.html.twig * field--node--created--link.html.twig x field--node--created.html.twig * field--node--link.html.twig * field--created.html.twig * field--created.html.twig * field.html.twig --> <!-- BEGIN OUTPUT from 'themes/contrib/stable/templates/field/field--node--created.html.twig' --> <span> <!-- THEME DEBUG --> <!-- THEME HOOK: 'time' --> <!-- BEGIN OUTPUT from 'themes/contrib/stable/templates/field/time.html.twig' --> <time datetime="2018-07-10T13:14:35+02:00" title="Tuesday, July 10, 2018 - 13:14">Tue, 07/10/2018 - 13:14</time> <!-- END OUTPUT from 'themes/contrib/stable/templates/field/time.html.twig' --> </span> <!-- END OUTPUT from 'themes/contrib/stable/templates/field/field--node--created.html.twig' --> <!-- THEME DEBUG --> <!-- THEME HOOK: 'links__node' --> <!-- FILE NAME SUGGESTIONS: * links--node.html.twig * links--node.html.twig x links.html.twig --> <!-- BEGIN OUTPUT from 'themes/custom/planet_foundated/templates/links.html.twig' --> <!-- END OUTPUT from 'themes/custom/planet_foundated/templates/links.html.twig' --> <!-- THEME DEBUG --> <!-- THEME HOOK: 'field' --> <!-- FILE NAME SUGGESTIONS: * field--node--body--link--rss.html.twig * field--node--body--link.html.twig * field--node--body.html.twig * field--node--link.html.twig * field--body.html.twig * field--text-with-summary.html.twig x field.html.twig --> <!-- BEGIN OUTPUT from 'themes/contrib/zurb_foundation/templates/field.html.twig' --> <div class="body field field--node-body field--name-body field--type-text-with-summary field--label-hidden field__item"><p>Google Structured Data docs</p> </div> <!-- END OUTPUT from 'themes/contrib/zurb_foundation/templates/field.html.twig' --> <!-- THEME DEBUG --> <!-- THEME HOOK: 'field' --> <!-- FILE NAME SUGGESTIONS: * field--node--field-link--link--rss.html.twig * field--node--field-link--link.html.twig * field--node--field-link.html.twig * field--node--link.html.twig * field--field-link.html.twig * field--link.html.twig x field.html.twig --> <!-- BEGIN OUTPUT from 'themes/contrib/zurb_foundation/templates/field.html.twig' --> <div class="text-content field field--node-field-link field--name-field-link field--type-link field--label-above"> <div class="field-label">Link</div> <div class="field__item"><a href="https://developers.google.com/search/docs/guides/intro-structured-data">https://developers.google.com/search/docs/guides/intro-structured-data</a></div> </div> <!-- END OUTPUT from 'themes/contrib/zurb_foundation/templates/field.html.twig' --> <!-- THEME DEBUG --> <!-- THEME HOOK: 'field' --> <!-- FILE NAME SUGGESTIONS: * field--node--field-tags--link--rss.html.twig * field--node--field-tags--link.html.twig * field--node--field-tags.html.twig * field--node--link.html.twig * field--field-tags.html.twig * field--entity-reference.html.twig x field.html.twig --> <!-- BEGIN OUTPUT from 'themes/contrib/zurb_foundation/templates/field.html.twig' --> <div class="field field--node-field-tags field--name-field-tags field--type-entity-reference field--label-above"> <div class="field-label">Tags</div> <div class="field__items"> <div class="field__item"><a href="/ca/etiquetes/documentacio" hreflang="ca">documentació</a></div> <div class="field__item"><a href="/ca/etiquetes/develop" hreflang="ca">develop</a></div> </div> </div> <!-- END OUTPUT from 'themes/contrib/zurb_foundation/templates/field.html.twig' --> <!-- THEME DEBUG --> <!-- THEME HOOK: 'field' --> <!-- FILE NAME SUGGESTIONS: * field--node--comment--link--rss.html.twig * field--node--comment--link.html.twig * field--node--comment.html.twig * field--node--link.html.twig x field--comment.html.twig x field--comment.html.twig * field.html.twig --> <!-- BEGIN OUTPUT from 'themes/contrib/stable/templates/field/field--comment.html.twig' --> <section> <h2>Add new comment</h2> <drupal-render-placeholder callback="comment.lazy_builders:renderForm" arguments="0=node&amp;1=6412&amp;2=comment&amp;3=comment" token="y1YX_WZkdde4v7F-tMLrz1q6cNdAbVuZAWiI6nuqqb4"></drupal-render-placeholder> </section> <!-- END OUTPUT from 'themes/contrib/stable/templates/field/field--comment.html.twig' --> Tue, 10 Jul 2018 11:14:35 +0000 kinta 6412 at https://planet.communia.org https://planet.communia.org/ca/content/google-structured-data-docs#comments Managing multiple drupals (7 and 8, composer and drush) https://planet.communia.org/ca/content/managing-multiple-drupals-7-and-8-composer-and-drush <!-- THEME DEBUG --> <!-- THEME HOOK: 'field' --> <!-- FILE NAME SUGGESTIONS: * field--node--title--blog--rss.html.twig * field--node--title--blog.html.twig x field--node--title.html.twig * field--node--blog.html.twig * field--title.html.twig * field--string.html.twig * field.html.twig --> <!-- BEGIN OUTPUT from 'themes/contrib/stable/templates/field/field--node--title.html.twig' --> <span>Managing multiple drupals (7 and 8, composer and drush)</span> <!-- END OUTPUT from 'themes/contrib/stable/templates/field/field--node--title.html.twig' --> <!-- THEME DEBUG --> <!-- THEME HOOK: 'field' --> <!-- FILE NAME SUGGESTIONS: * field--node--uid--blog--rss.html.twig * field--node--uid--blog.html.twig x field--node--uid.html.twig * field--node--blog.html.twig * field--uid.html.twig * field--entity-reference.html.twig * field.html.twig --> <!-- BEGIN OUTPUT from 'themes/contrib/stable/templates/field/field--node--uid.html.twig' --> <span> <!-- THEME DEBUG --> <!-- THEME HOOK: 'username' --> <!-- BEGIN OUTPUT from 'themes/custom/planet_foundated/templates/username.html.twig' --> <a href="/user/1" class="visually-hidden p-author h-card" rel="author" title="kinta">kinta <img src="" alt="kinta" /> </a> <a title="View user profile." href="/es/users/kinta">kinta</a> <!-- END OUTPUT from 'themes/custom/planet_foundated/templates/username.html.twig' --> </span> <!-- END OUTPUT from 'themes/contrib/stable/templates/field/field--node--uid.html.twig' --> <!-- THEME DEBUG --> <!-- THEME HOOK: 'field' --> <!-- FILE NAME SUGGESTIONS: * field--node--created--blog--rss.html.twig * field--node--created--blog.html.twig x field--node--created.html.twig * field--node--blog.html.twig * field--created.html.twig * field--created.html.twig * field.html.twig --> <!-- BEGIN OUTPUT from 'themes/contrib/stable/templates/field/field--node--created.html.twig' --> <span> <!-- THEME DEBUG --> <!-- THEME HOOK: 'time' --> <!-- BEGIN OUTPUT from 'themes/contrib/stable/templates/field/time.html.twig' --> <time datetime="2018-04-03T18:38:23+02:00" title="Tuesday, April 3, 2018 - 18:38">Tue, 04/03/2018 - 18:38</time> <!-- END OUTPUT from 'themes/contrib/stable/templates/field/time.html.twig' --> </span> <!-- END OUTPUT from 'themes/contrib/stable/templates/field/field--node--created.html.twig' --> <!-- THEME DEBUG --> <!-- THEME HOOK: 'field' --> <!-- FILE NAME SUGGESTIONS: * field--node--body--blog--rss.html.twig * field--node--body--blog.html.twig * field--node--body.html.twig * field--node--blog.html.twig * field--body.html.twig * field--text-with-summary.html.twig x field.html.twig --> <!-- BEGIN OUTPUT from 'themes/contrib/zurb_foundation/templates/field.html.twig' --> <div class="body field field--node-body field--name-body field--type-text-with-summary field--label-hidden field__item"><p><span><span>La mayoría de proyectos en drupal que hemos creado desde communia requieren un mantenimiento, y cuando crece la cantidad de proyectos a mantener se necesita una estrategia para poder hacer actuaciones en masa como pueden ser las instalaciones de módulos o librerías, actualizaciones, limpieza de caches o registros para monitorizar.</span></span></p> <p><span><span>Hasta la versión 8, drush permitía crear alias i agruparlos para realizar actuaciones por grupo. Por ejemplo se podía hacer un grupo @autoup que permitía actualizar Drupal que se sabía que en principio no tenían ningún motivo para dar errores en la actualización.</span></span></p> <p><span><span>Todo ello ha entrado en revisión con Drupal 8, en el momento en que drupal pasa a seguir la estrategia de innovación abierta que permite la inclusión de código no diseñado específicamente para drupal, también conocido como estrategia de innovación <span><em><a href="https://www.drupal.org/8/standards">Proudly Found Elsewhere</a></em></span> (symfony, easyrdf, doctrine, TWIG ...).Para orquestar todas las dependencias se hace vía <span><a href="https://getcomposer.org/doc/00-intro.md">composer</a></span> , y concretamente a partir de drupal 8 se recomienda instalar una <span><a href="https://github.com/drupal-composer/drupal-project">estructura (scaffolding)</a></span> .</span></span></p> <p><span> </span><span><span>Esto nos da estos cambios en la estructura del proyecto:</span></span></p> <p><span><img alt="Estructura de Drupal 7 vs Drupal(8) con drupal-composer " data-entity-type="file" data-entity-uuid="1d76cdb3-f239-45c4-a76d-4fc5ab50b8d9" src="/sites/default/files/inline-images/drupal7-vs-drupalcomposer_0.png" /></span></p> <p><span><span>En la que donde realmente se gestionan las dependencias es una carpeta por encima de la de web, así es en la carpeta raíz de drupal-project donde ejecutaremos composer para instalar dependencias.</span></span></p> <p><span><span> </span></span></p> <p><span><span>Todos estos cambios implican una nueva perspectiva para gestionar el proyecto, ya no podemos basarnos en drush, y de hecho la versión de drush 9.x <span><a href="https://drushcommands.com/drush-9x/pm/pm:download/">ya nos advierte</a></span> que instalar módulos con drush está abandonado.</span></span></p> <p><span><span>Como no he encontrado una herramienta para gestionar múltiples proyectos de composer, he creado la aplicación de consola <span><a href="https://github.com/aleixq/druman">druman</a></span> con el componente de symfony <span><a href="https://symfony.com/doc/current/console.html">console command</a></span> .Así se puede hacer una gestión de los proyectos sean basados en drush, o en composer.</span></span></p> <p><span><span><span><strong>Druman gestor de proyectos en drupal</strong></span></span></span></p> <p><span><span>Este programa se basa en una lista definida en yml que estará en ~ / .druman-aliases.yml, donde definimos algunas propiedades para cada proyecto: alias, path, groups, manager. </span></span></p> <p><span><span>Hay un ejemplo de un yml en la carpeta examples:</span></span></p> <ul><li> <p><span><span>alias: será el nombre con el que indexaremos, para poder acceder al proyecto.</span></span></p> </li> <li> <p><span><span>Path: es la ruta del proyecto, si usamos la estructura drupal-composer debemos dar la raíz del proyecto (no la de la web). En caso de que no usamos la estructura drupal-composer debemos poner la raíz de web.</span></span></p> </li> <li> <p><span><span>Groups: lista de grupos a los que pertenece el proyecto, por ejemplo autoup si queremos hacer un grupo de autoactualización o Hacked si queremos listar proyectos en los que debemos prestar especial atención a la hora de actualizar o instalar módulos. (Se puede poner los nombres que quieran, los que hay puestos son de ejemplo). </span></span></p> </li> <li> <p><span><span>Manager: Qué gestor utilizaremos para controlar dependencias:</span></span></p> <ul><li><strong>drush8</strong> Será útil para el comando projects:update (sin uso en comando projects:run), utiliza el gestor drush (v8) para actualizar siguiendo el procedimiento estándar de drupal 7 (no recomendado para drupal 8).</li> <li><strong>drupal-composer</strong> Será útil para el comando projects:update (sin uso en comando projects:run), utiliza el gestor composer para proceder con la actualización en estructuras drupal-composer.</li> <li><strong>drush8-alias</strong> Será útil cuando se actualiza (con el comando projects:update) y cuando se llaman comandos de drush (vía comando projects: run).Indicar el gestor drush8-alias es la vía para mantener un site remoto (o local) definido en los alias de drush, en lugar de reinventar la lógica de los alias remotos de drush, he optado por reaprovechar ello. Los alias serán tratados sin cambiar el directorio de proyecto (ya que no está definido path) ni haciendo un cambio de usuario, se hace tal como lo hacen los alias de drush (con los posibles problemas de permisos posteriores que pueden surgir). A la hora de ejecutar una orden siempre añadirá<br /><pre> <code class="language-bash">drush @alias</code></pre><p> por tanto los alias de drush y de druman deben coincidir, y solo se tendrá que indicar el comando de drush no toda la orden, por ejemplo:</p> <pre> <code class="language-bash">druman project:run -a project_x status</code></pre><p> en lugar de drush status<br />  </p></li> </ul></li> </ul><p><span><span><span><strong>Gestión de proyectos (sólo drupal 7) remotos.</strong></span></span></span></p> <p><span><span>Debemos prestar especial atención en que si en un proyecto utilizamos el manager drush8-alias, para gestionar proyectos remotos primero tendremos que definir el alias remoto tal como se hacía siempre con drush hasta la versión 8. Esto es así para no tener que re-escribir la lógica que utiliza drush para conectar a remotos (Para añadir un alias a drush hay información en: <span><a href="https://raw.githubusercontent.com/drush-ops/drush/8.x/examples/example.aliases.drushrc.php">https://raw.githubusercontent.com/drush-ops/drush/8. x / examples / example.aliases.drushrc.php</a></span> ).Así habrá que definir el alias en <span>~ / .drush / aliases.drushrc.php</span> y en ~ / .druman-aliases.yml , quizás en un futuro esto cambia para poder tirar composers en remoto.</span></span></p> <p><span> </span></p> <p><span><span>Si definimos un proyecto gestionado por <strong>drush8-alias</strong> el path deberá ponerse en blanco</span></span></p> <pre> <code class="language-yaml">alias: someexternal_com path: "" groups: hostingatx manager: drush8-alias</code></pre><p><span><span><span><strong>Listar proyectos</strong></span></span></span></p> <p><span><span>Para volcar la <strong>lista de proyectos</strong> podemos utilizar:</span></span></p> <pre> <code class="language-bash">druman projects:list </code></pre><p><span><span>Para <strong>filtrar</strong> la lista por grupo o por origen (local o remoto). Esta orden permite las siguientes opciones:</span></span></p> <pre> <code class="language-bash">druman projects: list -h Usage: projects: list [options] Options: -g, --group [= GROUP] List only projects of specified group -l, --local List only local projects -r, --remote List only remote projects -f, --full Show all fields from list: alias, path, management type and group.</code></pre><p><span><span><span><strong>Ejecutando ordenes en la raíz de los proyectos</strong></span></span></span></p> <p><span><span>A partir del listado de proyectos definidos en .druman-aliases.yml podemos realizar operaciones. Podemos tirar una orden en la raíz del proyecto vía:</span></span></p> <pre> <code class="language-bash">projects:run</code></pre><p><span><span><span>Tendremos las mismas opciones de filtrado que el listado y además la opción de seleccionar un único alias directamente. Las opciones son:</span></span></span></p> <pre> <code class="language-bash">druman projects:run -h Usage: projects:run [options] [-] [&lt;order&gt;] argumentos: order Command to run. Options: -g, --group [= GROUP] Run only on these projects which are members of specified group -a, --alias [= ALIAS] Run only on this specific alias -l, --local List only local projects -r, --remote List only remote projects -all, --all Run in all alias, excluding those using drush8-alias manager, if specified no filters will be used</code></pre><p> <span><span>Antes de ejecutar el comando lo hará habiendo <strong>cambiado de usuario</strong> en el que sea el propietario de la carpeta definida en el path del alias.</span></span></p> <p><span><span><span><strong>Ejecutando actualizaciones de los proyectos</strong></span></span></span></p> <p><span><span>Para actualizar hay el comando</span></span></p> <pre> <code class="language-bash">druman projects: update</code></pre><p><span><span><span>que permite las mismas opciones que la orden</span> <span>projects:</span><span>run.</span></span></span></p> <pre> <code class="language-bash">projects:update -h -g, --group [= GROUP] Run only on these projects which are members of specified group -a, --alias [= ALIAS] Run only on this specific alias -l, --local List only local projects -r, --remote List only remote projects -all, --all Run in all alias, excluding those using drush8-alias manager</code></pre><p><span><span>La forma en que actualiza los proyectos gestionados <span>por</span> <strong>drush8-alias</strong> o <strong>drush8</strong> sigue las órdenes para actualizar un <strong>drupal 7.La forma en que actualiza los proyectos gestionados por</strong> <strong>drupal-composer</strong> siguen el procedimiento para actualizar un <strong>drupal 8. </strong>Se puede ver los procedimientos en <span><a href="https://github.com/aleixq/druman/blob/master/src/Command/ManagerRunnerProjectsCommand.php">https://github.com/aleixq/druman/blob/master/src/Command/ManagerRunnerProjectsCommand.php</a></span> .</span></span></p> <p><span><span><span><strong>Qué queda pendiente:</strong></span></span></span></p> <ul><li> <p><span><span>Remotos, poder gestionar Drupal remotos con composer. Quizás la vía sería añadir propiedades ssh al .druman-aliases.yml. O igual que con los indicados con gestor drush8-alias definir un alias remoto como explica a <span><a href="https://raw.githubusercontent.com/drush-ops/drush/master/examples/example.site.yml">https://raw.githubusercontent.com/drush-ops/drush/master/examples/example.site.yml</a></span> .</span></span></p> </li> <li> <p><span><span>También poder añadir, quitar o actualizar proyectos del .druman-aliases.yml interactivamente.</span></span></p> </li> </ul></div> <!-- END OUTPUT from 'themes/contrib/zurb_foundation/templates/field.html.twig' --> <!-- THEME DEBUG --> <!-- THEME HOOK: 'field' --> <!-- FILE NAME SUGGESTIONS: * field--node--field-tags--blog--rss.html.twig * field--node--field-tags--blog.html.twig * field--node--field-tags.html.twig * field--node--blog.html.twig * field--field-tags.html.twig * field--entity-reference.html.twig x field.html.twig --> <!-- BEGIN OUTPUT from 'themes/contrib/zurb_foundation/templates/field.html.twig' --> <div class="field field--node-field-tags field--name-field-tags field--type-entity-reference field--label-inline clearfix"> <div class="field-label">Tags</div> <div class="field__items"> <div class="field__item"><a href="/ca/etiquetes/drupal" hreflang="ca">Drupal</a></div> <div class="field__item"><a href="/ca/etiquetes/tutorials" hreflang="ca">tutorials</a></div> <div class="field__item"><a href="/ca/etiquetes/documentacio" hreflang="ca">documentació</a></div> <div class="field__item"><a href="/ca/etiquetes/composer" hreflang="ca">composer</a></div> <div class="field__item"><a href="/ca/etiquetes/php" hreflang="ca">php</a></div> <div class="field__item"><a href="/ca/etiquetes/drush" hreflang="ca">drush</a></div> </div> </div> <!-- END OUTPUT from 'themes/contrib/zurb_foundation/templates/field.html.twig' --> <!-- THEME DEBUG --> <!-- THEME HOOK: 'links__node' --> <!-- FILE NAME SUGGESTIONS: * links--node.html.twig * links--node.html.twig x links.html.twig --> <!-- BEGIN OUTPUT from 'themes/custom/planet_foundated/templates/links.html.twig' --> <!-- END OUTPUT from 'themes/custom/planet_foundated/templates/links.html.twig' --> Tue, 03 Apr 2018 16:38:23 +0000 kinta 6396 at https://planet.communia.org https://planet.communia.org/es/content/managing-multiple-drupals-7-and-8-composer-and-drush#comments https://planet.communia.org/es/content/managing-multiple-drupals-7-and-8-composer-and-drush#comments