Creating a new latest-Drupal project with local-Drush, with all desired credentials in one go?

Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
I use Ubuntu 18.04 with Bash and Apache 2.4 and I desire to automate the entire process of creating a Drupal 8 with local Drush 9 project, at least after creating a database for it (which I usually create with PHPMyAdmin):
- Add data like
domain.tld, db name, db user name, db password and locality (localhost). - Create an Apache Virtual Host for the Drupal project based on the domain.
- Download and create a Drupal directory for the project under
/var/www/html/. - Change the directory's name to that of the domain and also create a proper
settings.phpwith the relevant details. - Restart the server.
I don't think the following Composer command is enough for that:
composer create-project drupal-composer/drupal-project
Is there a communally-supported way to achieve my aim?
untagged
migrated from drupal.stackexchange.com 13 mins ago
This question came from our site for Drupal developers and administrators.
 |Â
show 2 more comments
up vote
0
down vote
favorite
I use Ubuntu 18.04 with Bash and Apache 2.4 and I desire to automate the entire process of creating a Drupal 8 with local Drush 9 project, at least after creating a database for it (which I usually create with PHPMyAdmin):
- Add data like
domain.tld, db name, db user name, db password and locality (localhost). - Create an Apache Virtual Host for the Drupal project based on the domain.
- Download and create a Drupal directory for the project under
/var/www/html/. - Change the directory's name to that of the domain and also create a proper
settings.phpwith the relevant details. - Restart the server.
I don't think the following Composer command is enough for that:
composer create-project drupal-composer/drupal-project
Is there a communally-supported way to achieve my aim?
untagged
migrated from drupal.stackexchange.com 13 mins ago
This question came from our site for Drupal developers and administrators.
My apologies, yes that's possible. Exactly how you download it depends on your desired workflow (drupal-project is the most common, and more robust, but you can justdrush dl drupaltoo if you want). Installation is done viadrush site-install.drush si --helpwill give you the available parameters for that process
â Clive
yesterday
2
I can't comment on the votes (wasn't involved), but as we chatted about earlier, this just isn't the place to learn about Ansible, Vagrant, Docker, virtualisation, etc, regardless of whether you plan to use those technologies with Drupal. It's like asking a car mechanic to explain how the machines that produce cars work - they may be able to explain it, they may even have had experience using or building one, but they don't want to talk about that...they want to talk about fixing and maintaining cars. They assume that when you come to them, you already have a car
â Clive
20 hours ago
I think this is a false analogy because a Drupal developer (which as of 2018 I'm not) usually automates creation of Drupal projects. The concept of automation came time and again in Drupal conferences I were in... Docker and Asnible were heard of time and again in the lectures.
â JohnDoea
20 hours ago
2
The analogy is clumsy, definitely, but not false in my opinion. To be honest the only point I'm making is that you won't be able to learn how to use Docker, Ansible, Vagrant, etc, here, because that's not what this site is for. You'll no doubt find snippets and configurations to use with these technologies, even links to full projects like in a couple of the answers here, but you'll need to learn how to apply that piecemeal logic the way the rest of us did - in the documentation pages of each technology :)
â Clive
20 hours ago
2
I think if you are just getting started with devops, your best bet is to learn Docker since we're nearly at 2019. Volumes of docs out there for that. Also i think you are conflating Drush and Composer, which are two different tools. You can use Composer to scaffold out and control a Drupal project (see Drupal Composer or Acquia BLT), but neither require drush. Drush can be added to the project via Composer.
â Kevin
16 hours ago
 |Â
show 2 more comments
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I use Ubuntu 18.04 with Bash and Apache 2.4 and I desire to automate the entire process of creating a Drupal 8 with local Drush 9 project, at least after creating a database for it (which I usually create with PHPMyAdmin):
- Add data like
domain.tld, db name, db user name, db password and locality (localhost). - Create an Apache Virtual Host for the Drupal project based on the domain.
- Download and create a Drupal directory for the project under
/var/www/html/. - Change the directory's name to that of the domain and also create a proper
settings.phpwith the relevant details. - Restart the server.
I don't think the following Composer command is enough for that:
composer create-project drupal-composer/drupal-project
Is there a communally-supported way to achieve my aim?
untagged
I use Ubuntu 18.04 with Bash and Apache 2.4 and I desire to automate the entire process of creating a Drupal 8 with local Drush 9 project, at least after creating a database for it (which I usually create with PHPMyAdmin):
- Add data like
domain.tld, db name, db user name, db password and locality (localhost). - Create an Apache Virtual Host for the Drupal project based on the domain.
- Download and create a Drupal directory for the project under
/var/www/html/. - Change the directory's name to that of the domain and also create a proper
settings.phpwith the relevant details. - Restart the server.
I don't think the following Composer command is enough for that:
composer create-project drupal-composer/drupal-project
Is there a communally-supported way to achieve my aim?
untagged
untagged
asked yesterday
JohnDoea
127831
127831
migrated from drupal.stackexchange.com 13 mins ago
This question came from our site for Drupal developers and administrators.
migrated from drupal.stackexchange.com 13 mins ago
This question came from our site for Drupal developers and administrators.
My apologies, yes that's possible. Exactly how you download it depends on your desired workflow (drupal-project is the most common, and more robust, but you can justdrush dl drupaltoo if you want). Installation is done viadrush site-install.drush si --helpwill give you the available parameters for that process
â Clive
yesterday
2
I can't comment on the votes (wasn't involved), but as we chatted about earlier, this just isn't the place to learn about Ansible, Vagrant, Docker, virtualisation, etc, regardless of whether you plan to use those technologies with Drupal. It's like asking a car mechanic to explain how the machines that produce cars work - they may be able to explain it, they may even have had experience using or building one, but they don't want to talk about that...they want to talk about fixing and maintaining cars. They assume that when you come to them, you already have a car
â Clive
20 hours ago
I think this is a false analogy because a Drupal developer (which as of 2018 I'm not) usually automates creation of Drupal projects. The concept of automation came time and again in Drupal conferences I were in... Docker and Asnible were heard of time and again in the lectures.
â JohnDoea
20 hours ago
2
The analogy is clumsy, definitely, but not false in my opinion. To be honest the only point I'm making is that you won't be able to learn how to use Docker, Ansible, Vagrant, etc, here, because that's not what this site is for. You'll no doubt find snippets and configurations to use with these technologies, even links to full projects like in a couple of the answers here, but you'll need to learn how to apply that piecemeal logic the way the rest of us did - in the documentation pages of each technology :)
â Clive
20 hours ago
2
I think if you are just getting started with devops, your best bet is to learn Docker since we're nearly at 2019. Volumes of docs out there for that. Also i think you are conflating Drush and Composer, which are two different tools. You can use Composer to scaffold out and control a Drupal project (see Drupal Composer or Acquia BLT), but neither require drush. Drush can be added to the project via Composer.
â Kevin
16 hours ago
 |Â
show 2 more comments
My apologies, yes that's possible. Exactly how you download it depends on your desired workflow (drupal-project is the most common, and more robust, but you can justdrush dl drupaltoo if you want). Installation is done viadrush site-install.drush si --helpwill give you the available parameters for that process
â Clive
yesterday
2
I can't comment on the votes (wasn't involved), but as we chatted about earlier, this just isn't the place to learn about Ansible, Vagrant, Docker, virtualisation, etc, regardless of whether you plan to use those technologies with Drupal. It's like asking a car mechanic to explain how the machines that produce cars work - they may be able to explain it, they may even have had experience using or building one, but they don't want to talk about that...they want to talk about fixing and maintaining cars. They assume that when you come to them, you already have a car
â Clive
20 hours ago
I think this is a false analogy because a Drupal developer (which as of 2018 I'm not) usually automates creation of Drupal projects. The concept of automation came time and again in Drupal conferences I were in... Docker and Asnible were heard of time and again in the lectures.
â JohnDoea
20 hours ago
2
The analogy is clumsy, definitely, but not false in my opinion. To be honest the only point I'm making is that you won't be able to learn how to use Docker, Ansible, Vagrant, etc, here, because that's not what this site is for. You'll no doubt find snippets and configurations to use with these technologies, even links to full projects like in a couple of the answers here, but you'll need to learn how to apply that piecemeal logic the way the rest of us did - in the documentation pages of each technology :)
â Clive
20 hours ago
2
I think if you are just getting started with devops, your best bet is to learn Docker since we're nearly at 2019. Volumes of docs out there for that. Also i think you are conflating Drush and Composer, which are two different tools. You can use Composer to scaffold out and control a Drupal project (see Drupal Composer or Acquia BLT), but neither require drush. Drush can be added to the project via Composer.
â Kevin
16 hours ago
My apologies, yes that's possible. Exactly how you download it depends on your desired workflow (drupal-project is the most common, and more robust, but you can just
drush dl drupal too if you want). Installation is done via drush site-install. drush si --help will give you the available parameters for that processâ Clive
yesterday
My apologies, yes that's possible. Exactly how you download it depends on your desired workflow (drupal-project is the most common, and more robust, but you can just
drush dl drupal too if you want). Installation is done via drush site-install. drush si --help will give you the available parameters for that processâ Clive
yesterday
2
2
I can't comment on the votes (wasn't involved), but as we chatted about earlier, this just isn't the place to learn about Ansible, Vagrant, Docker, virtualisation, etc, regardless of whether you plan to use those technologies with Drupal. It's like asking a car mechanic to explain how the machines that produce cars work - they may be able to explain it, they may even have had experience using or building one, but they don't want to talk about that...they want to talk about fixing and maintaining cars. They assume that when you come to them, you already have a car
â Clive
20 hours ago
I can't comment on the votes (wasn't involved), but as we chatted about earlier, this just isn't the place to learn about Ansible, Vagrant, Docker, virtualisation, etc, regardless of whether you plan to use those technologies with Drupal. It's like asking a car mechanic to explain how the machines that produce cars work - they may be able to explain it, they may even have had experience using or building one, but they don't want to talk about that...they want to talk about fixing and maintaining cars. They assume that when you come to them, you already have a car
â Clive
20 hours ago
I think this is a false analogy because a Drupal developer (which as of 2018 I'm not) usually automates creation of Drupal projects. The concept of automation came time and again in Drupal conferences I were in... Docker and Asnible were heard of time and again in the lectures.
â JohnDoea
20 hours ago
I think this is a false analogy because a Drupal developer (which as of 2018 I'm not) usually automates creation of Drupal projects. The concept of automation came time and again in Drupal conferences I were in... Docker and Asnible were heard of time and again in the lectures.
â JohnDoea
20 hours ago
2
2
The analogy is clumsy, definitely, but not false in my opinion. To be honest the only point I'm making is that you won't be able to learn how to use Docker, Ansible, Vagrant, etc, here, because that's not what this site is for. You'll no doubt find snippets and configurations to use with these technologies, even links to full projects like in a couple of the answers here, but you'll need to learn how to apply that piecemeal logic the way the rest of us did - in the documentation pages of each technology :)
â Clive
20 hours ago
The analogy is clumsy, definitely, but not false in my opinion. To be honest the only point I'm making is that you won't be able to learn how to use Docker, Ansible, Vagrant, etc, here, because that's not what this site is for. You'll no doubt find snippets and configurations to use with these technologies, even links to full projects like in a couple of the answers here, but you'll need to learn how to apply that piecemeal logic the way the rest of us did - in the documentation pages of each technology :)
â Clive
20 hours ago
2
2
I think if you are just getting started with devops, your best bet is to learn Docker since we're nearly at 2019. Volumes of docs out there for that. Also i think you are conflating Drush and Composer, which are two different tools. You can use Composer to scaffold out and control a Drupal project (see Drupal Composer or Acquia BLT), but neither require drush. Drush can be added to the project via Composer.
â Kevin
16 hours ago
I think if you are just getting started with devops, your best bet is to learn Docker since we're nearly at 2019. Volumes of docs out there for that. Also i think you are conflating Drush and Composer, which are two different tools. You can use Composer to scaffold out and control a Drupal project (see Drupal Composer or Acquia BLT), but neither require drush. Drush can be added to the project via Composer.
â Kevin
16 hours ago
 |Â
show 2 more comments
3 Answers
3
active
oldest
votes
up vote
3
down vote
Have you already had a look at the ScriptHandler.php of drupal-composer/drupal-project?
It provides certain functions that are run via composer.json as post-install-cmd and post-update-cmd. You could extend the ScriptHandler.php to provide a post-create-project-cmd which runs your Drush stuff. Maybe with the help of Symfony's Console Component.
Sadly I should first take some PHP and Drupal-programming courses before I could comfortably understand what's going there. I know no programming besides some fundamental vanilla Bash and JS.
â JohnDoea
yesterday
add a comment |Â
up vote
2
down vote
I know it's not a perfect fit to your question, but one option is to start with geerlingguys Drupal Vagrant Box:
https://github.com/geerlingguy/drupal-vm
With this, you can set a custom config.yml to override the default.config.yml which will allow you to set variables/info such as DB name, DB pass, MySQL user, Site name, etc... It gets you pretty close to an all in one "up" kind of thing.
You can tell vagrant to install a DB or not. Install Drupal or not. You can have it use an existing DB on "up" command too.
Some example config.yml overrides (not tested):
---
vagrant_hostname: site_name.local
vagrant_machine_name: site_name_vm
drupal_site_name: "site_name"
drupal_account_pass: pass
drupal_db_name: site_name
php_version: "7.1"
vagrant_ip: 192.168.25.25
vagrant_memory: 4096
extra_packages:
- sqlite
- php-bcmath # This is needed for Commerce.
php_memory_limit: "256M"
php_display_errors: "On"
mysql_root_password: pass
drupal_account_name: admin
drupal_db_user: root
drupal_db_password: pass
Then it's just a matter of running vagrant up in your command line and it's possible to have vagrant install Drupal with DB and all creds/info.
You can take a look at the default.config.yml to see what's available and what you may want to override/set.
add a comment |Â
up vote
2
down vote
Consider using dbjpanda's drupal-on-docker; simple installation with everything automated. You just have to install docker and then:
- Clone the repository.
- Update the
.envfile with all of your information like domain name, db password, etc.
and you're good to go.
add a comment |Â
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
3
down vote
Have you already had a look at the ScriptHandler.php of drupal-composer/drupal-project?
It provides certain functions that are run via composer.json as post-install-cmd and post-update-cmd. You could extend the ScriptHandler.php to provide a post-create-project-cmd which runs your Drush stuff. Maybe with the help of Symfony's Console Component.
Sadly I should first take some PHP and Drupal-programming courses before I could comfortably understand what's going there. I know no programming besides some fundamental vanilla Bash and JS.
â JohnDoea
yesterday
add a comment |Â
up vote
3
down vote
Have you already had a look at the ScriptHandler.php of drupal-composer/drupal-project?
It provides certain functions that are run via composer.json as post-install-cmd and post-update-cmd. You could extend the ScriptHandler.php to provide a post-create-project-cmd which runs your Drush stuff. Maybe with the help of Symfony's Console Component.
Sadly I should first take some PHP and Drupal-programming courses before I could comfortably understand what's going there. I know no programming besides some fundamental vanilla Bash and JS.
â JohnDoea
yesterday
add a comment |Â
up vote
3
down vote
up vote
3
down vote
Have you already had a look at the ScriptHandler.php of drupal-composer/drupal-project?
It provides certain functions that are run via composer.json as post-install-cmd and post-update-cmd. You could extend the ScriptHandler.php to provide a post-create-project-cmd which runs your Drush stuff. Maybe with the help of Symfony's Console Component.
Have you already had a look at the ScriptHandler.php of drupal-composer/drupal-project?
It provides certain functions that are run via composer.json as post-install-cmd and post-update-cmd. You could extend the ScriptHandler.php to provide a post-create-project-cmd which runs your Drush stuff. Maybe with the help of Symfony's Console Component.
answered yesterday
leymannx
1313
1313
Sadly I should first take some PHP and Drupal-programming courses before I could comfortably understand what's going there. I know no programming besides some fundamental vanilla Bash and JS.
â JohnDoea
yesterday
add a comment |Â
Sadly I should first take some PHP and Drupal-programming courses before I could comfortably understand what's going there. I know no programming besides some fundamental vanilla Bash and JS.
â JohnDoea
yesterday
Sadly I should first take some PHP and Drupal-programming courses before I could comfortably understand what's going there. I know no programming besides some fundamental vanilla Bash and JS.
â JohnDoea
yesterday
Sadly I should first take some PHP and Drupal-programming courses before I could comfortably understand what's going there. I know no programming besides some fundamental vanilla Bash and JS.
â JohnDoea
yesterday
add a comment |Â
up vote
2
down vote
I know it's not a perfect fit to your question, but one option is to start with geerlingguys Drupal Vagrant Box:
https://github.com/geerlingguy/drupal-vm
With this, you can set a custom config.yml to override the default.config.yml which will allow you to set variables/info such as DB name, DB pass, MySQL user, Site name, etc... It gets you pretty close to an all in one "up" kind of thing.
You can tell vagrant to install a DB or not. Install Drupal or not. You can have it use an existing DB on "up" command too.
Some example config.yml overrides (not tested):
---
vagrant_hostname: site_name.local
vagrant_machine_name: site_name_vm
drupal_site_name: "site_name"
drupal_account_pass: pass
drupal_db_name: site_name
php_version: "7.1"
vagrant_ip: 192.168.25.25
vagrant_memory: 4096
extra_packages:
- sqlite
- php-bcmath # This is needed for Commerce.
php_memory_limit: "256M"
php_display_errors: "On"
mysql_root_password: pass
drupal_account_name: admin
drupal_db_user: root
drupal_db_password: pass
Then it's just a matter of running vagrant up in your command line and it's possible to have vagrant install Drupal with DB and all creds/info.
You can take a look at the default.config.yml to see what's available and what you may want to override/set.
add a comment |Â
up vote
2
down vote
I know it's not a perfect fit to your question, but one option is to start with geerlingguys Drupal Vagrant Box:
https://github.com/geerlingguy/drupal-vm
With this, you can set a custom config.yml to override the default.config.yml which will allow you to set variables/info such as DB name, DB pass, MySQL user, Site name, etc... It gets you pretty close to an all in one "up" kind of thing.
You can tell vagrant to install a DB or not. Install Drupal or not. You can have it use an existing DB on "up" command too.
Some example config.yml overrides (not tested):
---
vagrant_hostname: site_name.local
vagrant_machine_name: site_name_vm
drupal_site_name: "site_name"
drupal_account_pass: pass
drupal_db_name: site_name
php_version: "7.1"
vagrant_ip: 192.168.25.25
vagrant_memory: 4096
extra_packages:
- sqlite
- php-bcmath # This is needed for Commerce.
php_memory_limit: "256M"
php_display_errors: "On"
mysql_root_password: pass
drupal_account_name: admin
drupal_db_user: root
drupal_db_password: pass
Then it's just a matter of running vagrant up in your command line and it's possible to have vagrant install Drupal with DB and all creds/info.
You can take a look at the default.config.yml to see what's available and what you may want to override/set.
add a comment |Â
up vote
2
down vote
up vote
2
down vote
I know it's not a perfect fit to your question, but one option is to start with geerlingguys Drupal Vagrant Box:
https://github.com/geerlingguy/drupal-vm
With this, you can set a custom config.yml to override the default.config.yml which will allow you to set variables/info such as DB name, DB pass, MySQL user, Site name, etc... It gets you pretty close to an all in one "up" kind of thing.
You can tell vagrant to install a DB or not. Install Drupal or not. You can have it use an existing DB on "up" command too.
Some example config.yml overrides (not tested):
---
vagrant_hostname: site_name.local
vagrant_machine_name: site_name_vm
drupal_site_name: "site_name"
drupal_account_pass: pass
drupal_db_name: site_name
php_version: "7.1"
vagrant_ip: 192.168.25.25
vagrant_memory: 4096
extra_packages:
- sqlite
- php-bcmath # This is needed for Commerce.
php_memory_limit: "256M"
php_display_errors: "On"
mysql_root_password: pass
drupal_account_name: admin
drupal_db_user: root
drupal_db_password: pass
Then it's just a matter of running vagrant up in your command line and it's possible to have vagrant install Drupal with DB and all creds/info.
You can take a look at the default.config.yml to see what's available and what you may want to override/set.
I know it's not a perfect fit to your question, but one option is to start with geerlingguys Drupal Vagrant Box:
https://github.com/geerlingguy/drupal-vm
With this, you can set a custom config.yml to override the default.config.yml which will allow you to set variables/info such as DB name, DB pass, MySQL user, Site name, etc... It gets you pretty close to an all in one "up" kind of thing.
You can tell vagrant to install a DB or not. Install Drupal or not. You can have it use an existing DB on "up" command too.
Some example config.yml overrides (not tested):
---
vagrant_hostname: site_name.local
vagrant_machine_name: site_name_vm
drupal_site_name: "site_name"
drupal_account_pass: pass
drupal_db_name: site_name
php_version: "7.1"
vagrant_ip: 192.168.25.25
vagrant_memory: 4096
extra_packages:
- sqlite
- php-bcmath # This is needed for Commerce.
php_memory_limit: "256M"
php_display_errors: "On"
mysql_root_password: pass
drupal_account_name: admin
drupal_db_user: root
drupal_db_password: pass
Then it's just a matter of running vagrant up in your command line and it's possible to have vagrant install Drupal with DB and all creds/info.
You can take a look at the default.config.yml to see what's available and what you may want to override/set.
answered 23 hours ago
Prestosaurus
add a comment |Â
add a comment |Â
up vote
2
down vote
Consider using dbjpanda's drupal-on-docker; simple installation with everything automated. You just have to install docker and then:
- Clone the repository.
- Update the
.envfile with all of your information like domain name, db password, etc.
and you're good to go.
add a comment |Â
up vote
2
down vote
Consider using dbjpanda's drupal-on-docker; simple installation with everything automated. You just have to install docker and then:
- Clone the repository.
- Update the
.envfile with all of your information like domain name, db password, etc.
and you're good to go.
add a comment |Â
up vote
2
down vote
up vote
2
down vote
Consider using dbjpanda's drupal-on-docker; simple installation with everything automated. You just have to install docker and then:
- Clone the repository.
- Update the
.envfile with all of your information like domain name, db password, etc.
and you're good to go.
Consider using dbjpanda's drupal-on-docker; simple installation with everything automated. You just have to install docker and then:
- Clone the repository.
- Update the
.envfile with all of your information like domain name, db password, etc.
and you're good to go.
answered 21 hours ago
SkyRar
266
266
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f480616%2fcreating-a-new-latest-drupal-project-with-local-drush-with-all-desired-credenti%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
My apologies, yes that's possible. Exactly how you download it depends on your desired workflow (drupal-project is the most common, and more robust, but you can just
drush dl drupaltoo if you want). Installation is done viadrush site-install.drush si --helpwill give you the available parameters for that processâ Clive
yesterday
2
I can't comment on the votes (wasn't involved), but as we chatted about earlier, this just isn't the place to learn about Ansible, Vagrant, Docker, virtualisation, etc, regardless of whether you plan to use those technologies with Drupal. It's like asking a car mechanic to explain how the machines that produce cars work - they may be able to explain it, they may even have had experience using or building one, but they don't want to talk about that...they want to talk about fixing and maintaining cars. They assume that when you come to them, you already have a car
â Clive
20 hours ago
I think this is a false analogy because a Drupal developer (which as of 2018 I'm not) usually automates creation of Drupal projects. The concept of automation came time and again in Drupal conferences I were in... Docker and Asnible were heard of time and again in the lectures.
â JohnDoea
20 hours ago
2
The analogy is clumsy, definitely, but not false in my opinion. To be honest the only point I'm making is that you won't be able to learn how to use Docker, Ansible, Vagrant, etc, here, because that's not what this site is for. You'll no doubt find snippets and configurations to use with these technologies, even links to full projects like in a couple of the answers here, but you'll need to learn how to apply that piecemeal logic the way the rest of us did - in the documentation pages of each technology :)
â Clive
20 hours ago
2
I think if you are just getting started with devops, your best bet is to learn Docker since we're nearly at 2019. Volumes of docs out there for that. Also i think you are conflating Drush and Composer, which are two different tools. You can use Composer to scaffold out and control a Drupal project (see Drupal Composer or Acquia BLT), but neither require drush. Drush can be added to the project via Composer.
â Kevin
16 hours ago