Друпал Drush

Jun 14, 20100 likes520 views

Andrii Podanenko

DRUpal SHell

Ігор (Brun) Броновський

Основи роботи з drush

Що таке drush?

drush – оболонка командного рядка і Unix
інтерфейс сценаріїв для Drupal.
Справжній швейцарський армійський ніж,
який допоможе зробити життя легше для тих з
нас, хто вміє користуватись командним рядком
і проводить в ньому багато часу.

drush commands

Переглянути команди drush:
# drush help

або за адресою:
http://drupal.org/node/477684

Що дозволяє робити drush

1. Створення інсталяційних збірок
2. Встановдення/оновдення модулів
3. Відладка PHP/SQL коду
4. Робота з мультисатингом, темами,
контентом, виглядами(views), модулями*

Як зробити свою збірку?

drush dl drupal

drush dl cck views bueditor imce nodewords
pathauto search404 imageapi imagecache
imagefield tagadelic admin custom_breadcrumbs
filefield globalredirect token views_or visitors
highslide contemplate

drush dl uk

Включення/виключення
модулів

drush en views views_ui

drush dis views_ui

$SQL запит # drush sqlquery "SELECT * FROM {users} where uid=1" uid name pass mail mode sort threshold theme signature signature_format created access login status timezone language picture init data 1 Brun e10adc3949ba59adde56e057f20f883e admin@drupalcamp10.lap 0 0 0 0 1276336999 1276340858 1276337132 1 NULL admin@drupalcamp10.lap a:1:{s:18:"admin_compact_mode";b:1;}$

# drush vget
theme_default: "garland"
filter_html_1: 1
node_options_forum: Array
(
    [0] => status
)

site_name: "drupalcamp10.lap"
language_default: stdClass Object
(
    [language] => uk
    [name] => Ukrainian
    [native] => Українська
    [direction] => 0
    [enabled] => 1
    [plurals] => 3
    [formula] => (((($n%10)==1)&&(($n%100)!=11))?(0):((((($n%10)>=2)&&(($n%10)<=4))&&((($n%100)<10)||(($n%100)>=20)))?(1):2))
    [domain] =>
    [prefix] => uk
    [weight] => 0
    [javascript] => 78b227e743115aed55a7a2118ca6b65a
)

drupal_http_request_fails: FALSE
cron_last: 1276341233

Розробка модулів

# drush mb my_module menu cron write name="My module"
dep="forum views"

*Необхідний module_builder

Дякую за увагу!

Ігор (Brun) Броновський

http://brun.if.ua/

@BrunIF

The main focus of the presentation is to talk about Drizzle, both as a team and as a library. We will delve into the essence of Drizzle, analyze comments and feedback from social media and forums, and compare this tool to its competitors. During the presentation, we will explore the history of the creation of Drizzle ORM and learn how it has evolved to its current state. We will uncover its strengths and weaknesses and discuss why it may be a better choice for certain tasks and why, even with its advantages, it may not be suitable for others. In conclusion, we will discuss the future development plans for Drizzle and the ecosystem, with examples such as Drizzle Studio and other tools.

Coding for Future in Lutsk. JavaScript. Part 1Олег Вілігурський

KyivBSD 2009 - Creating a corporate instant messaging and information exchang...Oleksandr Drach

DrupalTour.Chernivtsi — Як написати якісний модуль для Drupal 7 (Taras Tsuper...Drupaltour

Lec10 11 ado-netcit-cit

Lecture 106 - SQL query languageAndrii Kopp

CSS по БЕМStfalcon Meetups

10 asp.net eleksdev

Golovinskiy hpc day 2011Volodymyr Saviak

3 1 Modbus ProtocolПупена Александр

Глобальні навчальні дні друпалAndrii Podanenko

природна і економна дорожня карта для переходу команди розробки на тест центр...Andrii Podanenko

Головні Принципи АвтоматизаціїAndrii Podanenko

Docker SQL Continuous Integration FlowAndrii Podanenko

This document summarizes the use of Docker for a multisite Drupal development workflow. Key points include: - Using Docker images and containers to share database layers between similar sites, improving build speeds. - Implementing a "lazy" continuous integration workflow with a parent PR builder and child builders for specific sites/tasks, run in parallel. - Introducing scripts to pull the latest database from production into a Docker image, then reusing that image for reinstalls rather than importing the full database each time. - Describing how the Docker-based approach works on both the CI server and local developer environments. - Noting some potential issues with Docker stability and leaving garbage,

Drupal 8 DevOps . Profile and SQL flows.Andrii Podanenko

Drupal 8 configuration development flowAndrii Podanenko

1. There are two main flows for Drupal 8 configuration management: the profile flow and the SQL flow. 2. The profile flow is used for initial project setup and involves exporting configurations from a staging site to a profile directory for installation. 3. The SQL flow is needed when adding content or complex module dependencies and cannot use configuration import since it would cause mismatches. Special tools are needed to import configurations and SQL data separately.

MoldCamp - multidimentional testing workflow. CIBox.Andrii Podanenko

CIBox is a continuous integration framework that allows for multidimensional testing before code is merged into the master branch. It provides tools and configurations for local development environments, automated testing, code reviews, and deployment. The framework uses Ansible playbooks to provision and configure Jenkins, Vagrant, databases, and other tools on a CI server. It also generates codebases with scripts for continuous integration testing in Vagrant virtual machines before code is merged.

CIbox - OpenSource solution for making your #devops betterAndrii Podanenko

This document describes an old and new development workflow for code reviews and continuous integration. The old workflow involved directly committing code to a shared master branch and deploying to a development server, while the new workflow uses feature branches, pull requests, and local virtual environments for development. It also introduces CIBox, an open source project that provides tools and automation to implement the new workflow, including provisioning a CI server and setting up initial project files.

DrupalCon Los Angeles - Continuous Integration ToolboxAndrii Podanenko

This document describes a multidimensional continuous integration (CI) workflow for Drupal projects using tools like Vagrant, Ansible, Jenkins, and other automation tools. It provides an overview of how code is developed locally, reviewed through pull requests, tested through automated jobs, and deployed across environments like development, staging, and production. The goal is to standardize and streamline the development process, improve quality, and reduce bottlenecks through automation. Key aspects covered include local development environments, database/configuration handling, code review process, automated testing, and deployment.

Drupal Continuous Integration WorkflowAndrii Podanenko

This document outlines a Drupal development workflow using continuous integration practices. It describes the technologies used such as GitHub, Jenkins, code sniffers and Vagrant. Development rules are established including requiring code reviews before merging to master and not allowing a PR creator to merge their own code. Team roles like architect, developer and project manager are defined. The workflow involves reinstalling from scratch for each build and using update paths for staging environments. Challenges with the workflow like CI server downtime and slow builds for large projects are also discussed.

More Related Content

Similar to Друпал Drush (12)

Theme24-jQueryОлег Вілігурський

.NET Platform. C# Basicseleksdev

"Drizzle: What Is It All About?", Alex Blokh, Dan KochetovFwdays

Coding for Future in Lutsk. JavaScript. Part 1Олег Вілігурський

KyivBSD 2009 - Creating a corporate instant messaging and information exchang...Oleksandr Drach

DrupalTour.Chernivtsi — Як написати якісний модуль для Drupal 7 (Taras Tsuper...Drupaltour

Lec10 11 ado-netcit-cit

Lecture 106 - SQL query languageAndrii Kopp

CSS по БЕМStfalcon Meetups

10 asp.net eleksdev

Golovinskiy hpc day 2011Volodymyr Saviak

3 1 Modbus ProtocolПупена Александр

Theme24-jQueryОлег Вілігурський

.NET Platform. C# Basicseleksdev

"Drizzle: What Is It All About?", Alex Blokh, Dan KochetovFwdays

Coding for Future in Lutsk. JavaScript. Part 1Олег Вілігурський

KyivBSD 2009 - Creating a corporate instant messaging and information exchang...Oleksandr Drach

DrupalTour.Chernivtsi — Як написати якісний модуль для Drupal 7 (Taras Tsuper...Drupaltour

Lec10 11 ado-netcit-cit

Lecture 106 - SQL query languageAndrii Kopp

CSS по БЕМStfalcon Meetups

10 asp.net eleksdev

Golovinskiy hpc day 2011Volodymyr Saviak

3 1 Modbus ProtocolПупена Александр

More from Andrii Podanenko (20)

Глобальні навчальні дні друпалAndrii Podanenko

природна і економна дорожня карта для переходу команди розробки на тест центр...Andrii Podanenko

Головні Принципи АвтоматизаціїAndrii Podanenko

Docker SQL Continuous Integration FlowAndrii Podanenko

Drupal 8 DevOps . Profile and SQL flows.Andrii Podanenko

Drupal 8 configuration development flowAndrii Podanenko

MoldCamp - multidimentional testing workflow. CIBox.Andrii Podanenko

CIbox - OpenSource solution for making your #devops betterAndrii Podanenko

DrupalCon Los Angeles - Continuous Integration ToolboxAndrii Podanenko

Drupal Continuous Integration WorkflowAndrii Podanenko

Сейчас самое время...ЖИТЬ!Andrii Podanenko

Start using vagrant now!Andrii Podanenko

This document discusses using Vagrant and provisioning tools like Puppet, Ansible, and PuPHPet.com to configure and provision virtual machines for local development. Vagrant provides a layer on top of virtual machine providers like VirtualBox to manage virtual machines via commands and configuration files. Provisioning tools like Puppet, Ansible, and PuPHPet.com can be used to automate the installation and configuration of software on Vagrant virtual machines. PuPHPet.com is a web interface that generates Puppet manifests and Vagrant configurations for common LAMP stack configurations.

Live deployment, ci, drupalAndrii Podanenko

1. The document discusses setting up a continuous integration workflow for Drupal projects using tools like Jenkins, Drush, and Vagrant. 2. It identifies problems with current development practices like code being merged without testing and different environments between dev and production. 3. The workflow proposed uses scripts to automate rebuilding development and production environments from source control, running tests, and deploying code.

Drupal contrib module maintainingAndrii Podanenko

This document discusses Drupal's project management tools and resources for module maintainers, including automated testing, documentation, issue tracking, and community support. It highlights how some popular modules grew large developer communities that fixed over 90% of critical bugs through these resources. The document encourages contributors to write tests before committing code and review patches through the issue queue. It also lists projects needing maintenance help and provides contact information.

Drupal codesprint kyiv drupal cafe 07.02.2013Andrii Podanenko

The Drupal Code Sprint event brings together Drupal developers to focus on collaborative coding and learning. Participants can choose between personal training sessions for $40 per hour, group training for $10 per hour, or sprint coding where the focus is on learning through coding. Attendees will gain knowledge of the Drupal infrastructure, opportunities for networking and community growth, and profit from connections and communication with fellow developers.

Drupal 8 what to wait fromAndrii Podanenko

This document summarizes some of the key features and changes in Drupal 8. It discusses the new Twig templating system, improved plugin and block systems, configuration management, multilingual improvements, and namespaced code structure. It also outlines initiatives to improve mobile support, accessibility, and front-end performance in Drupal 8. Several core modules have been removed, changed, or added to modernize the platform.

Do + ldo for developers(full)Andrii Podanenko

Диалоговый интенсив 2012 карпатыAndrii Podanenko

психолог в социальных медиаAndrii Podanenko

Ubercart7 views catalog ruAndrii Podanenko

Глобальні навчальні дні друпалAndrii Podanenko

природна і економна дорожня карта для переходу команди розробки на тест центр...Andrii Podanenko

Головні Принципи АвтоматизаціїAndrii Podanenko

Docker SQL Continuous Integration FlowAndrii Podanenko

Drupal 8 DevOps . Profile and SQL flows.Andrii Podanenko

Drupal 8 configuration development flowAndrii Podanenko

MoldCamp - multidimentional testing workflow. CIBox.Andrii Podanenko

CIbox - OpenSource solution for making your #devops betterAndrii Podanenko

DrupalCon Los Angeles - Continuous Integration ToolboxAndrii Podanenko

Drupal Continuous Integration WorkflowAndrii Podanenko

Сейчас самое время...ЖИТЬ!Andrii Podanenko

Start using vagrant now!Andrii Podanenko

Live deployment, ci, drupalAndrii Podanenko

Drupal contrib module maintainingAndrii Podanenko

Drupal codesprint kyiv drupal cafe 07.02.2013Andrii Podanenko

Drupal 8 what to wait fromAndrii Podanenko

Do + ldo for developers(full)Andrii Podanenko

Диалоговый интенсив 2012 карпатыAndrii Podanenko

психолог в социальных медиаAndrii Podanenko

Ubercart7 views catalog ruAndrii Podanenko

Друпал Drush

1. DRUpal SHell Ігор (Brun) Броновський Основи роботи з drush

2. Що таке drush? drush – оболонка командного рядка і Unix інтерфейс сценаріїв для Drupal. Справжній швейцарський армійський ніж, який допоможе зробити життя легше для тих з нас, хто вміє користуватись командним рядком і проводить в ньому багато часу.

3. Модуль Terminal

4. drush commands Переглянути команди drush: # drush help або за адресою: http://drupal.org/node/477684

5. Що дозволяє робити drush 1. Створення інсталяційних збірок 2. Встановдення/оновдення модулів 3. Відладка PHP/SQL коду 4. Робота з мультисатингом, темами, контентом, виглядами(views), модулями*

6. Як зробити свою збірку? drush dl drupal drush dl cck views bueditor imce nodewords pathauto search404 imageapi imagecache imagefield tagadelic admin custom_breadcrumbs filefield globalredirect token views_or visitors highslide contemplate drush dl uk

7. Вікно встановлення

8. Продовження встановлення

9. Включення/виключення модулів drush en views views_ui drush dis views_ui

10. SQL запит # drush sqlquery "SELECT * FROM {users} where uid=1" uid name pass mail mode sort threshold theme signature signature_format created access login status timezone language picture init data 1 Brun e10adc3949ba59adde56e057f20f883e [email protected] 0 0 0 0 1276336999 1276340858 1276337132 1 NULL [email protected] a:1:{s:18:"admin_compact_mode";b:1;}

11. # drush vget theme_default: "garland" filter_html_1: 1 node_options_forum: Array ( [0] => status ) site_name: "drupalcamp10.lap" language_default: stdClass Object ( [language] => uk [name] => Ukrainian [native] => Українська [direction] => 0 [enabled] => 1 [plurals] => 3 [formula] => (((($n%10)==1)&&(($n%100)!=11))?(0):((((($n%10)>=2)&&(($n%10)<=4))&&((($n%100)<10)||(($n%100)>=20)))?(1):2)) [domain] => [prefix] => uk [weight] => 0 [javascript] => 78b227e743115aed55a7a2118ca6b65a ) drupal_http_request_fails: FALSE cron_last: 1276341233

12. Розробка модулів # drush mb my_module menu cron write name="My module" dep="forum views" *Необхідний module_builder

13. Дякую за увагу! Ігор (Brun) Броновський http://brun.if.ua/ @BrunIF