DEV Community: Aastha Shrivastava

Setting up drupal9 multi-site with Lando

Aastha Shrivastava — Wed, 22 Sep 2021 14:12:08 +0000

Setting up a multi-site architecture can sound overwhelming and scary😱 with all the database setup and creating vhost for each site... it can become painful and daunting. But here is how you can setup a drupal 9 multi-site with single database using prefixes within 15 min(30 mins tops I swear!😬). So let's dive into it!

Pre-requisites:

Lando

Steps:

1. Start by downloading codebase for drupal9 by

composer create drupal/recommended-project
Inside your project folder run:

lando init   --source cwd   --recipe drupal9   --webroot .   --name <project-name>
 lando composer require drush/drush

2. Edit `.lando.yml` with following (example) content:

name: <project-name>
recipe: drupal9
config:
  webroot: web
  drush: ^10
  xdebug: true
  via: nginx
services:
  database:
    type: mariadb:10.5
proxy:
  appserver_nginx:
    - subsite1.lndo.site
    - subsite2.lndo.site
    - subsite3.lndo.site

Note: Replace with your project name.
The important thing to see here is proxy: appserver_nginx key which lists the URLs for our default and subsites which is equivalent to setting up vhost for each site, you may also need to add an entry for your default site like - <project-name>.lndo.site

3. Create folders for subsites in your `sites` directory

   mkdir subsite{1..3}

4. Copy `examples.sites.php` to `sites.php` and add entries for subsites in your `sites.php` file:

   $sites['subsite1.lndo.site'] = 'subsite1';
   $sites['subsite2.lndo.site'] = 'subsite2';
   $sites['subsite3.lndo.site'] = 'subsite3';

5. Copy settings.php to your default and subsites directories.

6. Run `lando rebuild`so it creates urls for our subsites.

7. Go to the respective URL on browser and install the default site first.

By default lando creates database with name drupal9 and username as password as drupal9 too and host as database so use these while installing the site:

Tip: you can quickly find info about configuration using lando info
Since this is default site we will leave the prefix empty.
Proceed and install the site.

8. Installing subsites

Go the URL for subsite, repeat step7, except this time also add the value in prefix field:

Proceed and install the site.

Note: Install site using browser instead of drush because drush will ask to drop and recreate the database for each site.

And We are all done!!!

In case you want to add more sites just repeat 2-6 and then 8 for your new site. And get it up and running in no time.

Remember we are doing everything here inside a docker container so if you want to check your databases for example, you will need to use lando mysql instead of just mysql and also the credentials will be the one which are created by lando rather than what you have on your system.

Let me know in the comments if you found this helpful! KThnxByee!👋🏼

Setting up drupal9 multi-site with DDEV

Aastha Shrivastava — Wed, 22 Sep 2021 13:04:34 +0000

Pre-requisites:

DDEV

Steps:

1. Make a new folder for your project and in your folder run:

 ddev config --project-type=drupal9 --docroot=web --create-docroot
 ddev composer create drupal/recommended-project
 ddev composer require drush/drush
 ddev restart

2. Create `.ddev/config.multisite.yaml` with following (example) content:

   additional_hostnames:
  - subsite1
  - subsite2
  - subsite3

This file contains list of URLs for our subsites which is equivalent to setting up vhost for each site.

3. Create folders for subsites in your `sites` directory

   mkdir subsite{1..3}

4. Copy `examples.sites.php` to `sites.php` and add entries for subsites in your `sites.php` file:

   $sites['subsite1.ddev.site'] = 'subsite1';
   $sites['subsite2.ddev.site'] = 'subsite2';
   $sites['subsite3.ddev.site'] = 'subsite3';

5. DDEV creates `settings.php` in `default` directory so copy this to your subsites

6. Since we are using single DB with prefixes add entry for db prefix in each of your subsite's `settings.php` after the line to import `settings.ddev.php`. Like this:

   // Automatically generated include for settings managed by ddev.
if (file_exists($app_root  . '/sites/default/settings.ddev.php') && getenv('IS_DDEV_PROJECT') == 'true') {
  include $app_root . '/sites/default/settings.ddev.php';
}
$databases['default']['default']['prefix'] = 'subsite1';

Note: By default ddev uses __DIR__ . '/settings.ddev.php' since it assumes settings.ddev.php is in the same directory, but since that is not the case with our subsites folders, we are using $app_root . '/sites/default/settings.ddev.php' instead.

7. Run `ddev restart` so it creates urls for our subsites.

8. Go to the respective URL on browser and install the site.

Note: Install site using browser instead of drush because drush will ask to drop and recreate the database for each site.

And We are all done!!!

In case you want to add more sites just repeat 2-8 for your new site. And get it up and running in no time.

In case you want to use multiste with multiple databse refer to this example.

Remember we are doing everything here inside a docker container so if you want to check your databases for example, you will need to use ddev mysql instead of just mysql and also the credentials will be the one which are created by DDEV rather than what you have on your system.

Let me know in the comments if you found this helpful! KThnxByee!👋🏼

Understanding Drupal's composer.json file line by line

Aastha Shrivastava — Thu, 05 Nov 2020 06:56:47 +0000

Understanding Drupal's composer.json file line by line

Name

{
    "name": "drupal/legacy-project",

name: denotes the name of the package.

Description

    "description": "Project template for Drupal 9 projects with composer following drupal/drupal layout",

description: denotes the short description about the package.

Type

    "type": "project",

type: denotes the type of a package, by default the type of a composer package is library. Here Drupal is of type project it means that drupal is full-fledged application rather than just a library which could be used by other projects.

License

    "license": "GPL-2.0-or-later",

license: denotes the type of license this project uses in this case GNU's General Public License.

Homepage

    "homepage": "https://www.drupal.org/project/drupal",

homepage: denotes the url of the package's website.

    "support": {
        "docs": "https://www.drupal.org/docs/user_guide/en/index.html",
        "chat": "https://www.drupal.org/node/314178"
        }

support: contains list of various resources to get support about the project.

docs: contains link of official documentation.
chat: contains link for the chat channel.

Repositories

    "repositories": [
        {
            "type": "composer",
            "url": "https://packages.drupal.org/8"
        }
    ]

repositories contains list of custom repositories to use, by default composer uses packagist repository to fetch packages. Here we are telling composer to fetch packages from https://packages.drupal.org/8.

Require

    "require": {
        "composer/installers": "^1.9",
        "drupal/core-composer-scaffold": "^9",
        "drupal/core-project-message": "^9",
        "drupal/core-recommended": "^9",
        "drupal/core-vendor-hardening": "^9"
    }

require contains list of packages required by this package. The current package could install only after all its requirements are installed.

Conflict

    "conflict": {
        "drupal/drupal": "*"
    },

conflict contains list of packages which conflict with this package for this version, this package will not get installed if any conflicting packages exists.

Minimum Stability

    "minimum-stability": "dev"

Minimum stability is used to filter packages based on their stability i.e stable, dev etc, the by default value of minimum-stability is stable. This means when you are trying to install a package via composer and the package is under development and there is no stable release yet, the composer will not install that package. Hence if you expect to work with package under development you should specify "minimum-stability as dev.

Prefer Stable

    "prefer-stable": true

If prefer-stable is set to true composer will perfer to install stable package version over unstable package versions.

Config

    "config": {
        "sort-packages": true
    }

Config is only supported with projects. config defines list of configurations for the project.

if sort-packages is set to true the require command will keep the packages sorted by name inside composer.json whenever it adds a new package.

Extra

    "extra": {
        .
        .
        .

extra contains any extra data which can be used by scripts. To access the data from script you can use:

$extra = $event->getComposer()->getPackage()->getExtra();

Let's try to understand each section in extra

`drupal-scaffold`

        "drupal-scaffold": {
            "locations": {
                "web-root": "./"
            }
        }

Here the drupal-scaffold configuration for composer-scaffold plugin

The location defines location of the web-root in this case it is ./.

`installer-paths`

There are various types of packages which can be installed by composer in drupal, for e.g core, libraries, modules, themes etc.

        "installer-paths": {
            "core": [
                "type:drupal-core"
            ],
            "libraries/{$name}": [
                "type:drupal-library"
            ]
            .
            .
            .
        }

The installer-paths specifies where a package should be places according to its type. For e.g a drupal-core package should be placed inside the core directory, and a drupal-library package should be placed inside a directory with its name in libraries directory and so on.

`drupal-core-project-message`

This section is used for The Drupal Project Message Plugin. The project message plugin is used to display messages after composer finishes installation, you can get the full documentation here.

        "drupal-core-project-message": {
            "include-keys": [
                "homepage",
                "support"
            ],
            "post-create-project-cmd-message": [
                "<bg=blue;fg=white>                                                         </>",
                "<bg=blue;fg=white>  Congratulations, you’ve installed the Drupal codebase  </>",
                .
                .
                "<bg=yellow;fg=black>Next steps</>:",
                "  * Install the site: https://www.drupal.org/docs/8/install",
                .
                .
            ]
        }
    }
}

The include-keys is used to tell plugin to output the structured support information from the composer.json file. Currently the plugin supports name, description, homepage and support keys only.

The post-create-project-cmd-message contains the formatted message to display on the command line after the project is successfully created/installed.

And that's all! We understood what each section represents in drupal's default composer file.

References

Official composer documentation
Anatomy of a Composer Project
Using Drupal's Composer Scaffold
Using Drupal's Project Message Composer Plugin

Automating Virtual Host setup on your server

Aastha Shrivastava — Wed, 04 Nov 2020 14:04:11 +0000

Are you also one of those who frequently need to setup VHosts in order to test,create etc new sites and you feel doing the whole process again and again is time consuming and well.. BORING? Then this article is for you!

Note: The script used in this article is written for any Linux distro with Apache server, but you may still get a general idea of how to use it for your requirements.

Here we will create a simple bash script to automate the whole vhost setup process which includes:

Creating a new folder for your website.
Creating configuration files for the website.
Configuring the hosts file and
Enabling the vhost.

Creating template files

Before we start working on our script we will need these template files which we use in the setup:

A template conf file to create configuration for the vhost.
A template index.html file for default homepage of our newly created vhost

This is how my template files looks like:
default-index.html



 <html>
   <head>
     <title>Home|New Virtual Host</title>
   </head>
   <body>
        <h1>Welcome!</h1> 
        You just created a new virtual host!<br>
        Go ahead and add some files in your brand new vhost
   </body>
 </html>

default-vhost.conf



<VirtualHost *:80>
        ServerName 127.0.0.x
        ServerAlias example.local
        ServerAdmin admin@example.local
        DocumentRoot /var/www/example.local

        ErrorLog ${APACHE_LOG_DIR}/error.log
        CustomLog ${APACHE_LOG_DIR}/access.log combined
</VirtualHost>

You can create similar files based on your requirements.

Now let's get started with the script.

Getting `sitename` and `host` from command line

Let's start by getting the input parameters as command line arguments. We will use the flags:

-s: for sitename
-h: for host

We will also use a flag -d (optional) in case user wants to create a new project directory for the vhost.

We will use getopts to get the arguments, if you are not familiar with getopts you can check out this article.

This is how we can take input from command line:



while getopts s:h:d flag
do
case "${flag}" in
                s) sitename=${OPTARG}
                        ;;
                h) host=${OPTARG}
                         ;;
                d) createdir=1
                        ;;
 echo "Added entry in hosts file"
               *) echo "Invalid option: -$flag" ;;
        esac
done

We are storing the values we got from input in sitename and host variable and setting createdir to 1.

Creating and configuring project directory

Next we will create a folder in /var/www and copy our default-index.html file in that folder:



if [[ $createdir -eq 1 ]]
then
  mkdir /var/www/$sitename
  cp default-index.html /var/www/$sitename/index.html

We are checking if user has specified the -d flag or not, you can remove the condition if you always want create a new directory for your vhost. You can also skip this step depending on your requirement.

Now that we have created the directory let's change the owner to current logged-in user:



  chown $SUDO_USER:$SUDO_USER /var/www/$sitename

This is because only the super user has permissions to create files and folders in var/www, so we are changing the owner of the folder so that the current user will have full control over the folder.

This script needs to be run using sudo, $SUDO_USER contains user name of user which is executing the script using sudo.

Now let's change the permission for



  chmod 755 /var/www/$sitename
fi

Creating configuration files

Now we will create the conf file for our site in /etc/apache2/sites-available/ using or default template:



cd /etc/apache2/sites-available/
cp default-vhost.conf $sitename.conf
sed -i "s/example.local/$sitename/g" $sitename.conf
sed -i "s/127.0.0.x/$host/g" $sitename.conf

Here sed or stream editor is a command line tool for editing, we are using sed to replace example.local with $sitename and 127.0.0.x with $host in our conf file.

Configuring hosts file

Currently your /etc/host must look like something like this :



127.0.0.1       localhost
.
.
.

# The following lines are desirable for IPv6 capable hosts
::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
.
.
.

We want to add the host and sitename before # The following lines are desirable... line. For this we will once again use the sed:



sed -i "0,/# The following lines are desirable for IPv6 capable hosts/s/^# The following lines are desirable.*/$host       $sitename\n&/" /etc/hosts

Enabling virtual host and restarting the server

Now let's enable our vhost using a2ensite command and reload apache:



a2ensite $sitename.conf
systemctl reload apache2
echo "All done! Visit your newly created virtual host at https://example123.local"

And that's it! Phew! We just created a simple script to automate vhost configuration. Let's go ahead and execute it:



sudo ./create-conf.sh -s example123.local -h 127.0.0.12 -d

All done! Visit your newly created virtual host at https://example123.local

Let's visit our newly created virtual host

Here is how our full script looks like:



#!/bin/bash

while getopts s:h:d flag

do

case "${flag}" in

                s) sitename=${OPTARG}

                        ;;

                h) host=${OPTARG}

                         ;;

                d) createdir=1

                        ;;

                *) echo "Invalid option: -$flag" ;;

        esac

done

# Create and configure folder in /var/www if option if option selected

if [[ $createdir -eq 1 ]]

then

  mkdir /var/www/$sitename

  echo "Folder /var/www/$sitename created"

  # Creating dummy landing page

  cp default-index.html /var/www/$sitename/index.html

  echo "Intitialized with index page"

# Changing owner and permission of the folder

  chown $SUDO_USER:$SUDO_USER /var/www/$sitename

  chmod 755 /var/www/$sitename

  echo "Modified permissions and owner"

fi

# Creating configuration files

cd /etc/apache2/sites-available/

cp default-vhost.conf $sitename.conf

sed -i "s/example.local/$sitename/g" $sitename.conf

sed -i "s/127.0.0.x/$host/g" $sitename.conf

echo "Configuration files created"

# Configuring hosts file

sed -i "0,/# The following lines are desirable for IPv6 capable hosts/s/^# The following lines are desirable.*/$host       $sitename\n&/" /etc/hosts

echo "Added entry in hosts file"

# Enabling virtual host and restarting the server

a2ensite $sitename.conf

systemctl reload apache2

echo "Restarted apache"

echo "All done! Visit your newly created virtual host at https://$sitename"

Final Thoughts

Though this script may not fully work with your requirement you can definitely get an idea of how to make one for yourself do let me know in the comments what you think about it!

References:

Setting up Virtual Host on Ubuntu 20
Taking command line arguments using flags in bash
Stream Editor to insert line
How to use sed to find and replace text in files in Linux / Unix shell

Setting up Virtual Host on Ubuntu 20

Aastha Shrivastava — Wed, 04 Nov 2020 11:45:03 +0000

What is Virtual Host:

Virtual host is a mechanism to set up multiple hosts in a single system the user feels that they are getting redirected to different locations when in reality their requests are sent to the same IP, just on different directories. Every virtual host is identified by virtualname. Virtual are useful because you can utilize a single IP location and single machine to host multiple websites. Let’s see how we can setup virtual host on our own machine in few simple steps

Pre-requisites:

In order to setup vhost you need to install and configure apache 2 on your ubuntu system. You can refer to this link to setup apache.

Step 1: Intitalizing and configuring directory

The first step is to create directory which contains the website i.e the document root of your site.

create the folder for your website in var/www/html:

sudo mkdir /var/www/mysite

You need to have root priviliges to create a folder in var/www/html

Now we need to change the permissions for mysite so that it can be accessed without root privilages. We will change the owner to current logged-in user to gain full access of mysite folder:

sudo chown $USER:$USER /var/www/mysite/

Where $USER contains name of current logged-in user.

Also we can ensure that mysite is readable by all the users:

sudo chmod 755 /var/www/mysite/

Step 2: Creating demo page in `mysite`

Now that we are all done with setting up directory let's add some content to it.
Note: You can skip this step if you have website content ready with you.

Create a file in mysite using nano or you can use any editor.

nano /var/www/mysite/index.html

Add some content like this:

<html>
<title>My Site</title>
<body>
<h1>Hello and Welcome to My Site<h2>
This is where it all started......
</body>
</html>

Press Ctrl+X and save the file.

Step 3: Creating configuration files for virtual host

We are all done with setting up content for our site. Let's move on to setup our virtual host file.

Apache provides a default file for virtual host called 000-default.conf present in /etc/apache2/sites-available/ which we can copy and modify a bit for our virtual host.
Let's copy the default file and open it in nano:

sudo cp /etc/apache2/sites-available/000-default.conf /etc/apache2/sites-available/mysite.local.conf

sudo nano /etc/apache2/sites-available/mysite.local.conf

You will see a bunch of parameters in this file. We will modify four of them for basic setup.
SeverAdmin -> the email of your website's admin
Sever Name -> the address of your website
Document Root -> the directory which contains the website.
Server Alias -> a sudo or virtual name that should be displayed on search bar while accessing the site.

<VirtualHost *:80>

        ServerName 127.0.0.2
        ServerAlias mysite.local
        ServerAdmin admin@mysite.com
        DocumentRoot /var/www/mysite

        ErrorLog ${APACHE_LOG_DIR}/error.log
        CustomLog ${APACHE_LOG_DIR}/access.log combined

</VirtualHost>

Save the file and exit.

Step 4: Enabling newly added virtual host

After configuring the virtual host file we have to enable it using a2ensite command (which rougly translates to apache2 enable site)
Change the directory and enable the site:

cd /etc/apache2/sites-available/
sudo a2ensite mysite.com.conf

To make the changes restart the apache server

sudo systemctl restart apache2

Step 5: Configuring hosts file

The last step is to configure /etc/hosts file which contains list of IP addresses and names. It acts like a local DNS file.
Let's open the file using nano:

sudo nano /etc/hosts

Now add the IP address and name of the site.
Note: the name should be same as the name of file for virtual host i.e mysite.local.conf

127.0.0.1       localhost
127.0.0.2       mysite.local

And that's it!!

Open browser and type http://mysite.local and you can access your site.

Congratulations! you just setup a virtual host.

References:

https://www.digitalocean.com/community/tutorials/how-to-set-up-apache-virtual-hosts-on-ubuntu-18-04-quickstart
https://linuxhint.com/install_apache_web_server_ubuntu/

Taking command line arguments using flags in bash

Aastha Shrivastava — Wed, 04 Nov 2020 11:17:52 +0000

In the previous article we created a simple bash script let's modify it a bit to accept command line arguments.
We will accept the name of directory which needs to be created and the path of directory whose files we have to list.
We will use flags to take input i.e -i for name of input directory whose contents will be listed and -o for output directory.

This is our current code:

#!/usr/bin/bash
# Script to create a directory in home with given name and a file containing list of files present in /var/www/html
NAME="Aastha"
mkdir ~/$NAME
echo `ls /var/www/html` > ~/$NAME/file_list.txt

Getting arguments using `getopts`

We will use get getopts function which returns a list of options(flags) with respective argument.
We will use a while to iterate through getopts

while getopts i:o: flag 
do

Here are we are specifying list of valid options as i:o: the : represents that an option need to be followed by a value.You can read more about getopts here.
flag is the iterator variable here. In bash the do followed by while statement specifies starting of block which contains satement to be executed by while. The ending of block is specified by done.

Storing argument values in variables

We will use switch case to assign values, based on options.

case "${flag}" in
                i) infolder=${OPTARG}
                        ;;
                o) outfolder=${OPTARG}
                         ;;
                *) echo "Invalid option: -$flag" ;;
        esac
done

The above will comapare $flag with i,o and * where * can be any thing other than i and o. The ;; indicates the end of a case. The ${OPTARG} contains the argument supplied for $flag option.
The esac indicates the end of the whole switch case block.

Replacing hard-coded values with new variables

mkdir ~/$outfolder 
ls $infolder > ~/$outfolder/file_list.txt

Final code

#!/usr/bin/bash
# Script to create a directory in home with name `$outfolder` and a file containing list of files present in`$infolder`
while getopts i:o: flag

do
        case "${flag}" in
                i) infolder=${OPTARG}
                        ;;
                o) outfolder=${OPTARG}
                         ;;
                *) echo "Invalid option: -$flag" ;;
        esac
done
mkdir ~/$outfolder 
ls $infolder > ~/$outfolder/file_list.txt

Getting started with Shell Scripting

Aastha Shrivastava — Wed, 04 Nov 2020 11:14:31 +0000

Shell scripting is a simple yet powerful way of performing some task using shell. A shell script is just like any program file which contains sequence of statements. Shell scripts can be useful when you want to execute a same set of commands everytime say for installing dependencies on multiple systems. What makes a shell script so powerfull is that you can directly write your shell commands as statements which allows you to do a lot of things ranging from linkinking two files for e.g getting some value from say a python script and supplying it as an input to say a php file, to monitoring the entire system. All this is possible because you are working on the system level.
Now that we know what can we do using shell script let's try to make one of our own.

Let's try to create a directory and list all the files in a specific directory.

Creating bash script step by step

1. Open your terminal and create a new script file.

Let's call our script file list_file.sh, every bash script has extension .sh.

vi list_files.sh

Press I to insert.

2. Specifying executable binary

The first line of the script contains the absolute path of the program by which it is executed.

Note: Although it is not necessary to specify program it is followed as a good practice.

Since we are creating a bash script the path will be /usr/bin/bash
Enter the following line:

#!/usr/bin/bash

3. Adding comments

You can add comments by adding # followed by comment in a bash script

# Script to create a directory in home with given name and a file containing list of files present in /var/www/html

4. Declaring variable

Now let's create a variable which contains name of the folder which we are going to create:

NAME="Aastha"

You can create variables just by writing variable_name = value, no need to specify data type.

5. Creating folder

Now let's create a folder in home directory:

mkdir ~/$NAME

Notice that NAME is preceeded by $, here $NAME represents value stored in NAME variable.

6. Generating file with list of files present in /var/www/html

We can use echo followed by text, to print some text on stdout(Standard Outoput) but we can also use it to add some text in a specified file using > operator like this:

echo `ls /var/www/html` > ~/$NAME/file_list.txt

Here ~/$NAME/file_list.txt is the name of out put file which contains result of ls /var/www/html.
The ` denotes that echo will first evaluate the expression and then use its value.

The whole file will look like this:

#!/usr/bin/bash
# Script to create a directory in home with given name and a file containing list of files present in /var/www/html
NAME="Aastha"
mkdir ~/$NAME
echo `ls /var/www/html` > ~/$NAME/file_list.txt

7. Saving the file

We are done with all the statements, let's save and close the file. Press Esc then type :wq that is write and quit and press enter.

8. Executing the script

To execute the script first we will need to change its permissions by:

chmod +x list_files.sh

Which will grant executing permissions to all.

Now let's execute the script:

./list_files.sh

And that's it! You can see a file is created in the specified directory.

This was just a basic shell script in the next article we'll see how to take command line arguments using flags

Resetting admin password in Drupal

Aastha Shrivastava — Wed, 04 Nov 2020 09:28:17 +0000

Often when you are working on a local Drupal site you may forget your admin password and you haven't setup SMTP yet, in this case there are multiple ways to recover your admin password, this article we'll see how to reset the admin password by changing password in database and resetting password using drush.

Using SQL/Database

Prerequisite:

Access to your drupal site's codebase i.e the project folder of your drupal site
Access to database which is used by your drupal site

Generating password hash

Go to your site's document root and execute

php core/scripts/password-hash.sh 'newpasswd'

Replace 'newpasswd' with your password.

You will see the output similar to this:

password: newpasswd         hash: $S$Eno1EhlPNMqE2RfDOBT13tzGCAdN9PgKqJFGI.4sBSj1XgJfPH68

$S$Eno1EhlPNMqE2RfDOBT13tzGCAdN9PgKqJFGI.4sBSj1XgJfPH68 is the hash which we need to update in the database.

Updating password in database

You can either use GUI like phpmyadmin and change pass = $S$Eno1EhlPNMqE2RfDOBT13tzGCAdN9PgKqJFGI.4sBSj1XgJfPH68 in the users_field_data.

The uid of admin is 1 by default in drupal. The same mechanism can be used to change password of any user by supplying the appropriate uid.

OR
You can use mysql command line and execute:

UPDATE users_field_data 
SET pass='$S$Eno1EhlPNMqE2RfDOBT13tzGCAdN9PgKqJFGI.4sBSj1XgJfPH68' 
WHERE uid = 1;

Clearing the cache

Even after updating the password in users_field_data table,may still won't allow you to login this is because the login system is referring to the password stored in cache_entity table and not users_field_data, so you will need to delete the record in cache_entity using gui, or by using mysql command line and executing:

DELETE FROM cache_entity WHERE cid = 'values:user:1';

For drupal 7 or older

Generating password hash

Go to your site's document root and execute

php scripts/password-hash.sh 'newpasswd'

Replace 'newpasswd' with your password.

Updating password in database

You need to make the changes mentioned for Drupal 8 or newer in users table instead of users_field_data

If you have exceeded your login attempts you may need to delete corresponding records from flood table.
This flood table records username and ip which has failed login attempts.

Using Drush

If you have drush installed with your drupal installation you can easily reset the password for any user even the admin

There are 2 ways of using drush to change password:

Using drush to generate password reset link

You can generate a link to reset with the following command:

drush uli --name=<username>

drush uli --uid=<user id>

Replace and with the username and the id of the user whose password needs to get reset. If you do not specify uid or name drush will operate on the user with uid 1.

This will generate a one-time login link which looks like this:
http://default/user/reset/2/1604915661/Ua9e50at_ggrlLqr5ulcX39CbpLjLO85Tczhz8nbdCM/login
Replace default with your hostname or IP and log in.

Alternatively, you can use option --uri <hostname/IP> to specify the hostname or IP of your website and drush will generate the link for your site.

Copy this link on your browser and you will get the password reset screen.

Using drush to reset password through the command line

You can change the password of someuser to somepass like this:

drush user:password someuser "somepass"

References:

Resetting the administrator password with sql-query in Drupal 8
Resetting the administrator password with sql-query (Drupal 7)
Recovering the administrator password

Using github Workflow to Recognize Community Contributions

Aastha Shrivastava — Thu, 17 Sep 2020 20:38:42 +0000

My Workflow

Leader-board for Community Contributions
Actions Used:

checkout
setup-python
peter-evans/close-issue
peter-evans/create-or-update-comment

Submission Category:

Wacky Wildcards

Yaml File or Link to Code

{% github https://github.com/devcpune/Awesome-DevC-Contributors/blob/master/.github/workflows/main.yml %}

Additional Resources / Info

Workflow is currently in use by Awesome-DevC-Contributors
Journey of the Leaderboard workflow

How I used github workflow to recognize community contributions(Part-1)

Aastha Shrivastava — Thu, 17 Sep 2020 20:36:14 +0000

Recently Developer Circles Facebook has concluded its Open Source Immersion Program, and we at DevC Pune thought to make a repository to recognize all the PRs made by the community during this program and decided to make a repository which has leader-board for the same, but collecting all the data was difficult and there comes GitHub workflows to the rescue which made ease the process of collecting data about PR and publishing on the repository. Enough with the stories! Let's talk about what we actually did.

Before starting let's understand what is a workflow and how it works.

What is a GitHub Workflow?

A GitHub Workflow is a mechanism used for automating your projects life cycle, remember event handling in other languages like Java, JavaScript etc? Yep this is the same just with GitHub events.

Instead of onClick, onHover etc we have events like: PR opened, Issue opened, Issue edited etc.
When an event occurs, the workflow has a list of jobs to be executed, in a job we can do some processing, and use some actions, which are just like functions in our regular programming language.

How does a GitHub Workflow works?

Every workflow needs to have a .yml which contains various sections of identifying the event and list of jobs reacting based upon the event. The yml file can even call another script to do some processing. When a job is executed it creates an instance of you repo on cloud, like a docker image, and now this is instance is just like a copy of your repo on a local machine, once you are done with processing you have to push the changes back to GitHub to see the changes. So you can use this instance to to perform anything which you do on your terminal.

Creating a yml file

In the first line we have to specify the name of the workflow:

name: add-project
# This workflow gets executed when someone opens an issue for adding a project

You can also add some comment to describe what that workflow is doing.

We can define an event on which a workflow will be triggered like this:

on:
  issues:
      types: [opened,edited]

Now comes the list of jobs, we can define a job as:

jobs:
  add_project_job:
    if: startsWith(github.event.issue.title, 'add|')
    name: add-project
    runs-on: ubuntu-latest
    steps:

Here add_project_job is the name of job. We can also specify condition which decides if certain job will be executed or not.
The runs-on parameter specify the environment which will be created to run the job. Next we have to define steps which will be executed inside a job.

And that is the basic structure of a GitHub workflow. We'll discuss the whole workflow in detail in the next part! Till then keep automating!

References:

Official Documentation
Link to Full Code

DEV Community: Aastha Shrivastava

Setting up drupal9 multi-site with Lando

Pre-requisites:

Steps:

1. Start by downloading codebase for drupal9 by

2. Edit .lando.yml with following (example) content:

3. Create folders for subsites in your sites directory

4. Copy examples.sites.php to sites.php and add entries for subsites in your sites.php file:

5. Copy settings.php to your default and subsites directories.

6. Run lando rebuildso it creates urls for our subsites.

7. Go to the respective URL on browser and install the default site first.

8. Installing subsites

Setting up drupal9 multi-site with DDEV

Pre-requisites:

Steps:

1. Make a new folder for your project and in your folder run:

2. Create .ddev/config.multisite.yaml with following (example) content:

3. Create folders for subsites in your sites directory

4. Copy examples.sites.php to sites.php and add entries for subsites in your sites.php file:

5. DDEV creates settings.php in default directory so copy this to your subsites

6. Since we are using single DB with prefixes add entry for db prefix in each of your subsite's settings.php after the line to import settings.ddev.php. Like this:

7. Run ddev restart so it creates urls for our subsites.

8. Go to the respective URL on browser and install the site.

Understanding Drupal's composer.json file line by line

Understanding Drupal's composer.json file line by line

Name

Description

Type

License

Homepage

Repositories

Require

Conflict

Minimum Stability

Prefer Stable

Config

Extra

drupal-scaffold

installer-paths

drupal-core-project-message

References

Automating Virtual Host setup on your server

Creating template files

Getting sitename and host from command line

Creating and configuring project directory

Creating configuration files

Configuring hosts file

Enabling virtual host and restarting the server

Final Thoughts

References:

Setting up Virtual Host on Ubuntu 20

What is Virtual Host:

Pre-requisites:

Step 1: Intitalizing and configuring directory

Step 2: Creating demo page in mysite

Step 3: Creating configuration files for virtual host

Step 4: Enabling newly added virtual host

Step 5: Configuring hosts file

References:

Taking command line arguments using flags in bash

Getting arguments using getopts

Storing argument values in variables

Replacing hard-coded values with new variables

Final code

Getting started with Shell Scripting

Creating bash script step by step

1. Open your terminal and create a new script file.

2. Specifying executable binary

3. Adding comments

4. Declaring variable

5. Creating folder

6. Generating file with list of files present in /var/www/html

7. Saving the file

8. Executing the script

Resetting admin password in Drupal

Using SQL/Database

Prerequisite:

Generating password hash

Updating password in database

Clearing the cache

2. Edit `.lando.yml` with following (example) content:

3. Create folders for subsites in your `sites` directory

4. Copy `examples.sites.php` to `sites.php` and add entries for subsites in your `sites.php` file:

6. Run `lando rebuild`so it creates urls for our subsites.

2. Create `.ddev/config.multisite.yaml` with following (example) content:

3. Create folders for subsites in your `sites` directory

4. Copy `examples.sites.php` to `sites.php` and add entries for subsites in your `sites.php` file:

5. DDEV creates `settings.php` in `default` directory so copy this to your subsites

6. Since we are using single DB with prefixes add entry for db prefix in each of your subsite's `settings.php` after the line to import `settings.ddev.php`. Like this:

7. Run `ddev restart` so it creates urls for our subsites.

`drupal-scaffold`

`installer-paths`

`drupal-core-project-message`

Getting `sitename` and `host` from command line

Step 2: Creating demo page in `mysite`

Getting arguments using `getopts`