Introduction

This guide explores how to use Vagrant Virtual Machine to its fullest potential, from setup to advanced scenarios. In the world of software development, virtualized environments play a crucial role in ensuring consistency, portability, and scalability. However, managing these environments can often feel daunting. Enter Vagrant, a powerful tool designed to simplify and streamline the process of creating and managing virtualized development environments. Whether you’re a seasoned developer or a beginner, Vagrant offers an intuitive and efficient solution to virtual machine (VM) management.

What is Vagrant?

Vagrant is an open-source tool developed by HashiCorp that provides a consistent workflow for building and managing virtualized environments. By leveraging simple configuration files, Vagrant automates the setup of virtual machines across different providers such as VirtualBox, VMware, or even cloud platforms like AWS.

Key Benefits of Using Vagrant:

• Portability: Share the same development environment across teams.
• Reproducibility: Consistently recreate environments to avoid the “it works on my machine” issue.
• Ease of Use: Simple configuration files and commands make Vagrant beginner-friendly.
• Integration: Works seamlessly with popular provisioning tools like Ansible, Puppet, or Chef.

How Vagrant Works

Vagrant relies on a configuration file, Vagrantfile, which describes the virtual environment, including the base operating system, resources, networking, and provisioning steps. With just a few commands, you can initialize, configure, and start a virtual machine.

Getting Started with Vagrant

Step 1: Install Vagrant

1. Download Vagrant: Visit the official Vagrant website to download the installer for your operating system.
2. Install a Virtualization Provider: Vagrant requires a provider like VirtualBox. Install it before proceeding.

Step 2: Initialize a New Vagrant Project

1. Open a terminal and navigate to your project directory.
2. Run:

vagrant init hashicorp/bionic64

This initializes a new Vagrantfile using Ubuntu 18.04 as the base box.

Step 3: Start the Virtual Machine

Run the following command to start your VM:

vagrant up

Step 4: Access Your Virtual Machine

To connect to your VM, use:

vagrant ssh

Configuring Vagrant Virtual Machine Environments

The Vagrantfile

The Vagrantfile is the core of any Vagrant project. Here’s a breakdown of its key components:

Example:

Vagrant.configure("2") do |config|
  # Define the base box
  config.vm.box = "hashicorp/bionic64"

  # Configure networking
  config.vm.network "forwarded_port", guest: 80, host: 8080

  # Allocate resources
  config.vm.provider "virtualbox" do |vb|
    vb.memory = "1024"
    vb.cpus = 2
  end

  # Provisioning
  config.vm.provision "shell", inline: <<-SHELL
    apt-get update
    apt-get install -y apache2
  SHELL
end

Networking Options

• Port Forwarding: Forward ports from the host to the guest machine.
• Private Networking: Assign a static IP address for local development.
• Public Networking: Expose the VM to your local network.

Provisioning

Vagrant supports provisioning tools to automate software installation:

• Shell Scripts:
  • config.vm.provision "shell", inline: "echo Hello, World!"
• Ansible or Puppet: Integrate your favorite configuration management tools.

Advanced Use Cases

Multi-Machine Environments

Set up multiple VMs in a single project, ideal for microservices or testing clusters.

Example:

Vagrant.configure("2") do |config|
  config.vm.define "web" do |web|
    web.vm.box = "hashicorp/bionic64"
    web.vm.network "forwarded_port", guest: 80, host: 8080
  end

  config.vm.define "db" do |db|
    db.vm.box = "hashicorp/bionic64"
    db.vm.network "private_network", ip: "192.168.33.10"
  end
end

Running Cloud-Based VMs

Leverage Vagrant plugins like vagrant-aws to manage virtual machines on AWS.

Troubleshooting Common Issues

1. “Vagrant up” hangs

• Ensure your virtualization provider is properly installed.
• Verify your Vagrantfile syntax.

2. SSH connection errors

• Run vagrant ssh-config to inspect SSH settings.

Frequently Asked Questions

What are Vagrant Boxes?

Vagrant boxes are pre-configured virtual machine images. Popular options include:

• hashicorp/bionic64 (Ubuntu 18.04)
• debian/buster64 (Debian)

Can I use Vagrant without VirtualBox?

Yes! Vagrant supports multiple providers, including VMware, Docker, and AWS.

How do I share my Vagrant environment with teammates?

Commit your Vagrantfile and any provisioning scripts to a version control system like Git.

External Resources

• Vagrant Documentation
• VirtualBox Downloads
• HashiCorp Community

Conclusion

Vagrant revolutionizes the way developers manage virtualized environments, offering a streamlined and repeatable workflow. By mastering its configuration and tools, you can save time, enhance collaboration, and improve development consistency. Start your journey with Vagrant today and unlock the power of virtual machines for your projects!  Thank you for reading the DevopsRoles page!

Introduction

In the fast-paced world of DevOps, efficiency and automation are critical. Vagrant is a powerful tool that simplifies creating, managing, and deploying virtualized environments. With Vagrant, developers can quickly spin up development environments that mirror production, improving consistency and reducing configuration time. Vagrant tutorial explores essential features, how it fits into DevOps workflows, and walks through setting up and using Vagrant in real-world scenarios.

What is Vagrant?

Vagrant is an open-source tool designed to create and configure lightweight, reproducible, and portable development environments. It automates the setup and configuration of virtual machines (VMs), making it easier to replicate environments across different machines. Vagrant is widely used in DevOps as it provides a streamlined approach for managing infrastructure as code (IaC), reducing inconsistencies between development, staging, and production environments.

Why Use Vagrant in DevOps?

• Consistency: Ensures all team members work in identical environments.
• Portability: Environments can be moved between machines seamlessly.
• Automation: Automates VM setup, configuration, and provisioning.
• Simplicity: Simplifies managing and destroying virtual environments with one command.

Prerequisites for Using Vagrant

Before we dive into using Vagrant, make sure you have the following installed:

1. Vagrant: Download Vagrant.
2. VirtualBox (or any provider supported by Vagrant): Download VirtualBox.
3. Terminal or Command Prompt: For running Vagrant commands.

Getting Started with Vagrant Tutorial

Step 1: Install Vagrant and VirtualBox

To start, download and install Vagrant and VirtualBox, which Vagrant uses by default as the virtualization provider. After installation, verify that Vagrant is installed correctly by running:

vagrant --version

Step 2: Initialize a Vagrant Project

In a new directory, initialize a Vagrant project. This will create a Vagrantfile—a configuration file that defines the environment.

mkdir my-vagrant-project
cd my-vagrant-project
vagrant init

This creates a Vagrantfile in the project directory, which is essential for configuring your Vagrant environment.

Step 3: Edit the Vagrantfile

Open the Vagrantfile in your preferred text editor. Modify the following lines to specify the box (VM image) and networking options:

Vagrant.configure("2") do |config|
  config.vm.box = "ubuntu/bionic64"
  config.vm.network "private_network", type: "dhcp"
end

In this example, we are using the ubuntu/bionic64 box and setting up a private network. You can find other pre-built boxes at Vagrant Cloud.

Step 4: Start the Vagrant Environment

With the Vagrantfile configured, run the following command to start the Vagrant environment:

vagrant up

This command will download the specified box if it’s not already available locally and then create and configure the VM.

Step 5: SSH into the VM

To interact with your virtual machine, SSH into it with the command:

vagrant ssh

This opens a terminal session directly into the VM, where you can perform additional configurations or install software.

Step 6: Suspend, Halt, or Destroy the VM

When you’re done, you can suspend, halt, or destroy the VM to save resources.

• Suspend: vagrant suspend
  • Saves the state of the VM to resume later.
• Halt: vagrant halt
  • Shuts down the VM.
• Destroy: vagrant destroy
  • Completely removes the VM.

Vagrant for DevOps: Advanced Use Cases

1. Provisioning with Shell Scripts

Vagrant supports provisioning using shell scripts, making it easy to install software and perform configurations during the VM setup.

Example Vagrantfile with shell provisioning:

Vagrant.configure("2") do |config|
  config.vm.box = "ubuntu/bionic64"
  config.vm.provision "shell", inline: <<-SHELL
    sudo apt-get update
    sudo apt-get install -y nginx
  SHELL
end

This setup will automatically install Nginx when the VM is created.

2. Multi-Machine Environments

Vagrant allows you to define multiple VMs within a single Vagrantfile, useful for simulating complex environments like microservices architectures.

Example Vagrantfile for multi-machine setup:

Vagrant.configure("2") do |config|
  config.vm.define "web" do |web|
    web.vm.box = "ubuntu/bionic64"
    web.vm.network "private_network", ip: "192.168.33.10"
    web.vm.provision "shell", inline: "sudo apt-get install -y nginx"
  end

  config.vm.define "db" do |db|
    db.vm.box = "ubuntu/bionic64"
    db.vm.network "private_network", ip: "192.168.33.11"
    db.vm.provision "shell", inline: "sudo apt-get install -y mysql-server"
  end
end

In this setup, we have two VMs: a web server and a database server, each with a private IP address.

3. Using Ansible with Vagrant

Vagrant can integrate with Ansible for more complex provisioning, ideal for larger DevOps environments.

Example Vagrantfile with Ansible provisioning:

Vagrant.configure("2") do |config|
  config.vm.box = "ubuntu/bionic64"
  config.vm.provision "ansible" do |ansible|
    ansible.playbook = "playbook.yml"
  end
end

The playbook.yml file defines the configuration managed by Ansible, making it easy to apply configurations across multiple VMs.

Common Vagrant Commands Cheat Sheet

Command	Description
vagrant init	Initialize a new Vagrant project
vagrant up	Start and provision the VM
vagrant ssh	SSH into the VM
vagrant suspend	Suspend the VM
vagrant halt	Halt the VM
vagrant destroy	Destroy the VM
vagrant provision	Re-run provisioning scripts on the VM
vagrant reload	Restart the VM and apply any configuration changes

Frequently Asked Questions

What is Vagrant used for?

Vagrant is used to create, configure, and manage virtualized environments for development and testing, ensuring consistency across different stages of software development.

How does Vagrant work with DevOps?

Vagrant allows DevOps teams to automate environment setup, streamline testing, and ensure consistent configurations between development, staging, and production.

Can Vagrant work with Docker?

Yes, Vagrant supports Docker as a provider, allowing users to create and manage Docker containers instead of virtual machines.

What are the system requirements for Vagrant?

Vagrant requires a 64-bit operating system and compatible virtualization software (e.g., VirtualBox, VMware, Docker).

How is Vagrant different from Docker?

Vagrant primarily manages virtual machines, while Docker manages containers. Vagrant is ideal for managing full VM environments, while Docker is optimized for lightweight, isolated containers.

External Resources

• Vagrant Official Documentation
• Vagrant Cloud – Find and use pre-built Vagrant boxes.
• HashiCorp – The company behind Vagrant and other DevOps tools.

Conclusion

Vagrant is a powerful and versatile tool that has become an essential component of modern DevOps practices. It simplifies environment setup, promotes consistency across team members, and integrates well with other DevOps tools. By following this tutorial, you can leverage Vagrant to automate and manage virtualized environments effortlessly. Whether you are a developer looking to streamline local development or a DevOps engineer aiming for consistent deployments, Vagrant is a valuable asset in your toolkit. Thank you for reading the DevopsRoles page!

Introduction

In this article, we will guide you through the process of Add second drive in Vagrant. Adding an additional drive can be beneficial for various purposes, such as expanding storage space or separating application data. We will go through each step in detail so that you can easily implement and manage your new drive in the Vagrant environment.

Why Add a Second Drive in Vagrant?

Adding a second drive to your Vagrant environment can provide numerous benefits:

• Increased Storage: Expand your VM’s storage capacity.
• Data Segregation: Separate different types of data or applications.
• Improved Performance: Enhance I/O performance by distributing data across multiple drives.
• Backup and Recovery: Simplify backup and recovery processes by isolating critical data.

Prerequisites

Before you begin, ensure you have the following:

• Vagrant installed on your system.
• A Vagrant box is configured and running.
• Basic knowledge of Vagrant commands and configuration.

Step-by-Step Guide to Add Second drive in Vagrant

Step 1: Check the Collected Data – Disk File

First, list the contents of your VirtualBox VM directory to check the existing disk files:

$ ls -l /home/huupv/VirtualBox\ VMs/build6_default_1464167769486_18523/

Step 2: Login and Check the Disks in the OS

Once logged in, you can check the existing disks in the OS itself with the following command:

# fdisk -l

Step 3: Stop the Vagrant Box

Before making any changes, halt the Vagrant box:

$ vagrant halt

Step 4: Edit the Vagrantfile

Edit your Vagrantfile to add the second drive. Include the following configuration:

config.vm.provider "virtualbox" do |vb|
  # Display the VirtualBox GUI when booting the machine
  # vb.gui = true

  # Customize the amount of memory on the VM:
  # vb.memory = "1024"

  second_disk = "/tmp/build6box-disk2.vmdk"
  vb.customize ['createhd', '--filename', second_disk, '--size', 500 * 1024]
  vb.customize ['storageattach', :id, '--storagectl', 'SATA Controller', '--port', 1, '--device', 0, '--type', 'hdd', '--medium', second_disk]
end

Step 5: Run the Vagrant Box

Start the Vagrant box with the updated configuration:

$ vagrant up

Step 6: Verify the New Disk

Check the file of the new disk on the host machine:

$ file /tmp/build6box-disk2.vmdk

And verify the drive within the Vagrant box itself using fdisk:

# fdisk -l | grep Disk

Following these steps, you will successfully add a second drive to your Vagrant setup.

Conclusion

Adding a second drive in Vagrant is a straightforward process when you follow the specific instructions. From editing the Vagrantfile to restarting the Vagrant box, each step ensures that the new drive is created and attached successfully. With the ability to easily expand and customize, Vagrant helps you manage and develop your virtual environment efficiently. Try applying these steps to improve your system configuration today. Thank you for reading the DevopsRoles page!

Introduction

In this tutorial, How to fix vagrant SSH permission denied. I use Host OS Windows 11 and Vagrant. I have to deploy a VM using Vagrant. Finish, login ssh to guest OS.

vagrant up command error as below:

vagrant@127.0.0.1: Permission denied (publickey,gssapi-keyex,gssapi-with-mic)

Understanding the Error

What is the “vagrant ssh Permission denied” Error?

The “vagrant SSH Permission denied” error occurs when the Vagrant fails to establish an SSH connection to the virtual machine. This can be caused by various issues such as incorrect SSH keys, misconfigured Vagrantfiles, or permission issues.

Common Causes

1. Incorrect SSH Key Permissions: The SSH key file might not have the correct permissions.
2. Missing or Incorrect SSH Keys: The SSH key might be missing or not properly configured.
3. Vagrantfile Misconfiguration: The Vagrantfile may have incorrect settings.
4. User Permissions: The user running Vagrant may not have the necessary permissions.

My Environment

• Host OS: Windows 11 or Linux/Ubuntu/Redhat
• Vagrant version: 2.2.18
• Vagrant provider: VirtualBox
• Boxes Vagrant: rockylinux/8

For example, My Vagrantfile

# -*- mode: ruby -*-
# vi: set ft=ruby :

Vagrant.configure("2") do |config|

  config.vm.box = "rockylinux/8"
  config.vm.network "forwarded_port", guest: 80, host: 8888
  config.vbguest.auto_update = false
end

Deploy a Virtual Machine

vagrant up

The output terminal is as follows:

How do fix vagrant SSH permission denied

I add configure “config.ssh.insert_key = false” into the Vagrantfile file

After changing my Vagrantfile as the content below

# -*- mode: ruby -*-
# vi: set ft=ruby :

Vagrant.configure("2") do |config|

  config.vm.box = "rockylinux/8"
  config.ssh.insert_key = false
  config.vm.network "forwarded_port", guest: 80, host: 8888
  config.vbguest.auto_update = false
end

The result

Frequently Asked Questions

Why am I getting a “vagrant SSH permission denied” error?

This error occurs when Vagrant fails to establish an SSH connection to the virtual machine, often due to incorrect SSH key permissions, missing keys, misconfigured Vagrantfiles, or user permission issues.

How do I fix SSH key permission issues in Vagrant?

You can fix SSH key permission issues by setting the correct permissions with the command chmod 600 ~/.ssh/id_rsa.

Can I regenerate the SSH key for Vagrant?

Yes, you can regenerate the SSH key for Vagrant by destroying the existing machine, removing the old key, and reinitializing Vagrant.

How do I manually add an SSH key to the SSH agent?

Start the SSH agent eval "$(ssh-agent -s)" and add your SSH key with ssh-add ~/.ssh/id_rsa.

Should I update Vagrant and its plugins?

Yes, updating Vagrant and its plugins can resolve many issues, including SSH connection problems. Use vagrant plugin update and vagrant box update to update them.

Conclusion

Encountering the “vagrant SSH Permission denied” error can be frustrating, but with the steps outlined in this guide, you should be able to resolve it efficiently. From checking SSH key permissions to updating Vagrant, these solutions cover both basic and advanced troubleshooting methods. Ensuring smooth operation of your Vagrant environments is crucial for a seamless development workflow. Thank you for reading the DevopsRoles page!

Introduction

Setting up WordPress with Vagrant has become a go-to solution for developers seeking a reliable, consistent, and portable environment for web development. Vagrant simplifies the process of creating and configuring virtual environments, ensuring that your WordPress projects are not only portable but also identical across various systems. This guide walks you through the step-by-step process of setting up WordPress Vagrant, from basic installation to advanced configurations.

In this tutorial, I’m set up a WordPress Vagrant, using vagrant box ubuntu with Nginx + MariaDB + WordPress. Vagrant the essential for DevOps Roles.

Benefits of Using Vagrant for WordPress Development

1. Consistent Environments

• Ensures uniformity between development, staging, and production environments.
• Avoids the common “works on my machine” problem.

2. Portable and Reproducible

• Easily share development environments across teams.
• Rapidly recreate environments in case of errors or new projects.

3. Integration with Popular Tools

• Works seamlessly with VirtualBox, Docker, and other virtualization tools.
• Supports provisioning tools like Ansible, Chef, and Puppet.

Prerequisites

Before diving into the setup, ensure you have the following:

Required Tools

• VirtualBox: Virtualization software.
• Vagrant: Tool to manage virtual environments.
• A code editor like Visual Studio Code.
• Basic understanding of command-line operations.

System Requirements

• At least 8GB of RAM.
• 20GB of free disk space.
• A stable internet connection.

Step-by-Step Guide to Setting Up WordPress with Vagrant

The structures files and folders wordpress vagrant as below:

[huupv@localhost project]$ pwd
/home/huupv/project
[huupv@localhost project]$ ls -F
keys/ nginx/ Vagrantfile var/
mysql/ php/ VAGRANT_ENV/ wp/

To configure Vagrantfile

vim Vagrantfile

The content as below:

VAGRANTFILE_API_VERSION = "2"
Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
config.vm.box = "ubuntu/xenial64"
config.vm.hostname = "wp"
config.ssh.insert_key = false
#config.vm.boot_timeout = 800
#config.ssh.username = vagrant
#config.ssh.password = vagrant
#config.ssh.private_key_path = ["keys/.ssh/vagrant_rsa", "~/.vagrant.d/insecure_private_key"]
#config.vm.provision "file", source: "keys/.ssh/vagrant_rsa.pub", destination: "~/.ssh/authorized_keys"
config.vm.provision :shell, path: "VAGRANT_ENV/bootstrap.sh"
config.vm.network "forwarded_port", guest: 80, host: 8888
config.vm.network :public_network, :bridge => "eth1", :auto_config => false
config.vm.provider :virtualbox do |vb|
# Set VM memory size
vb.customize ["modifyvm", :id, "--memory", "512"]
# these 2 commands massively speed up DNS resolution, which means outbound
# connections don't take forever (eg the WP admin dashboard and update page)
vb.customize ["modifyvm", :id, "--natdnshostresolver1", "on"]
vb.customize ["modifyvm", :id, "--natdnsproxy1", "on"]
end
end

To configure file vagrant bootstrap.sh

vim VAGRANT_ENV/bootstrap.sh

The content as below:

#!/bin/bash
echo "Vagrant box (Ubuntu 16.04 + nginx + php7.0 + MariaDB + WordPress."
 echo "Updating apt-get"
 sudo apt-get -y update
# Nginx
 echo "Installing Nginx"
 sudo apt-get install -y nginx
# MySQL
 echo "Preparing for MySQL Installation"
 sudo apt-get install -y debconf-utils
 sudo debconf-set-selections << "mysql-server mysql-server/root_password password root"
 sudo debconf-set-selections << "mysql-server mysql-server/root_password_again password root" echo "Installing MySQL" #sudo apt-get install -y mysql-server-5.7
 sudo apt-get install -y mariadb-server mariadb-client php7.0-mysql
 sudo rm -f /etc/mysql/my.cnf
 sudo rm -f /etc/alternatives/my.cnf
 sudo cp /vagrant/mysql/my.cnf /etc/alternatives/my.cnf
 sudo ln -s /etc/alternatives/my.cnf /etc/mysql/my.cnf
 ls -ll /etc/mysql/my.cnf
 echo "Installing PHP and MySQL module"
 sudo apt-get install -y php-fpm php-mysql
# Nginx Config
 echo "Overwriting default Nginx config to work with PHP"
 sudo rm -rf /etc/nginx/sites-available/default
 cp /vagrant/nginx/default.conf /etc/nginx/sites-available/default
# php cli
 sudo sed -i "s/error_reporting = .*/error_reporting = E_ALL/" /etc/php/7.0/fpm/php.ini
 sudo sed -i "s/display_errors = .*/display_errors = On/" /etc/php/7.0/cli/php.ini
 sudo sed -i "s/memory_limit = .*/memory_limit = 30M/" /etc/php/7.0/cli/php.ini
 sudo sed -i "s/;date.timezone.*/date.timezone = UTC/" /etc/php/7.0/cli/php.ini
# php fpm
 sudo sed -i "s/error_reporting = .*/error_reporting = E_ALL/" /etc/php/7.0/fpm/php.ini
 sudo sed -i "s/display_errors = .*/display_errors = On/" /etc/php/7.0/fpm/php.ini
 sudo sed -i "s/;cgi.fix_pathinfo=1/cgi.fix_pathinfo=0/" /etc/php/7.0/fpm/php.ini
 sudo sed -i "s/memory_limit = .*/memory_limit = 30M/" /etc/php/7.0/fpm/php.ini
 sudo sed -i "s/upload_max_filesize = .*/upload_max_filesize = 100M/" /etc/php/7.0/fpm/php.ini
 sudo sed -i "s/post_max_size = .*/post_max_size = 100M/" /etc/php/7.0/fpm/php.ini
 sudo sed -i "s/;date.timezone.*/date.timezone = UTC/" /etc/php/7.0/fpm/php.ini
# Restarting Nginx for config to take effect
 echo "Restarting Nginx for changes to take effect"
 sudo service nginx restart

echo "Setting Ubuntu (user) password to \"vagrant\""
echo "ubuntu:vagrant" | chpasswd
# Services restart
 sudo systemctl restart mysql.service
 sudo systemctl restart nginx.service
 sudo systemctl restart php7.0-fpm.service
sudo mysql -u root -p -e 'show databases'
 #Create wordpress databases
 bash /vagrant/mysql/create_database.sh
 #To install and configure wordpress
 cd /tmp
 curl -O https://wordpress.org/latest.tar.gz
 tar xzvf latest.tar.gz
 sudo cp /tmp/wordpress/wp-config-sample.php /tmp/wordpress/wp-config.php
 mkdir /tmp/wordpress/wp-content/upgrade
 sudo cp -a /tmp/wordpress/* /var/www/html
 sudo find /var/www/html -type d -exec chmod g+s {} \;
 sudo chmod g+w /var/www/html/wp-content
 sudo chmod -R g+w /var/www/html/wp-content/themes
 sudo chmod -R g+w /var/www/html/wp-content/plugins
 sudo rm -f /var/www/html/wp-config.php
 sudo cp /vagrant/wp/wp-config.php /var/www/html/wp-config.php
 sudo usermod -a -G www-data ubuntu
 sudo chown -R ubuntu:www-data /var/www/html
 sudo systemctl restart nginx.service
 echo "Cleaning up additional setup files and logs"
 #sudo rm -r /var/www/html
 #sudo rm /var/www/ubuntu-xenial-16.04-cloudimg-console.log

To configure MySQL my.cf file

vim mysql/my.cnf

The content as below:

[client]
port = 3306
socket = /var/run/mysqld/mysqld.sock
[mysqld_safe]
socket = /var/run/mysqld/mysqld.sock
nice = 0

[mysqld]
user = mysql
pid-file = /var/run/mysqld/mysqld.pid
socket = /var/run/mysqld/mysqld.sock
port = 3306
basedir = /usr
datadir = /var/lib/mysql
tmpdir = /tmp
lc-messages-dir = /usr/share/mysql
skip-external-locking
bind-address = 0.0.0.0
key_buffer_size = 16M
max_allowed_packet = 16M
thread_stack = 192K
thread_cache_size = 8
myisam-recover = BACKUP
query_cache_limit = 1M
query_cache_size = 16M
log_error = /var/log/mysql/error.log
expire_logs_days = 10
max_binlog_size = 100M
[mysqldump]
quick
quote-names
max_allowed_packet = 16M

[mysql]
[isamchk]
key_buffer_size = 16M
!includedir /etc/mysql/conf.d/

To create a database for WordPress

vim mysql/create_database.sh

The content as below:

#!/usr/bin/env bash
if [ ! -z "wordpress" ] ; then
echo "creating database"
 sudo mysql -u root -p'root' -e "CREATE DATABASE IF NOT EXISTS wordpress;"
if [ ! -z "wp_db_user" ]; then
 echo " adding custom user"
 sudo mysql -u root -p'root' -e "GRANT ALL ON wordpress.* TO 'wp_db_user'@'localhost' IDENTIFIED BY '123456789'"
 sudo mysql -u root -p'root' -e "FLUSH PRIVILEGES;"
 sudo mysql -u root -p'root' -e 'show databases;'
 fi
else
 echo "No database name specified - skipping db creation"
fi

To configure file wp-config.php for WordPress vagrant

vim wp/wp-config.php

The content as below:

<?php
define('DB_NAME', 'wordpress');
/** MySQL database username */
 define('DB_USER', 'wp_db_user');
/** MySQL database password */
 define('DB_PASSWORD', '123456789');
/** MySQL hostname */
 define('DB_HOST', 'localhost');
/** Database Charset to use in creating database tables. */
 define('DB_CHARSET', 'utf8');
/** The Database Collate type. Don't change this if in doubt. */
 define('DB_COLLATE', '');
 define('AUTH_KEY', 'put your unique phrase here');
 define('SECURE_AUTH_KEY', 'put your unique phrase here');
 define('LOGGED_IN_KEY', 'put your unique phrase here');
 define('NONCE_KEY', 'put your unique phrase here');
 define('AUTH_SALT', 'put your unique phrase here');
 define('SECURE_AUTH_SALT', 'put your unique phrase here');
 define('LOGGED_IN_SALT', 'put your unique phrase here');
 define('NONCE_SALT', 'put your unique phrase here');
 $table_prefix = 'wp_';
 define('WP_DEBUG', false);
 /** Absolute path to the WordPress directory. */
 if ( !defined('ABSPATH') )
 define('ABSPATH', dirname(__FILE__) . '/');
/** Sets up WordPress vars and included files. */
 require_once(ABSPATH . 'wp-settings.php');
 define('FS_METHOD', 'direct');

To configure file nginx.conf

vim nginx/default.conf

The content as below:

server {
 listen 80 default_server;
 listen [::]:80 default_server ipv6only=on;
 root /var/www/html/;
 index index.php index.html index.htm;
 client_max_body_size 20M;
 server_name devopsroles.com;
 location / {
 try_files $uri $uri/ /index.php?$args;
 }
 error_page 404 /404.html;
 error_page 500 502 503 504 /50x.html;
 location = /50x.html {
 root /usr/share/nginx/html;
 }
 location ~ \.php$ {
 try_files $uri =404;
 fastcgi_split_path_info ^(.+\.php)(/.+)$;
 fastcgi_pass unix:/var/run/php/php7.0-fpm.sock;
 fastcgi_index index.php;
 include fastcgi_params;
 fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
 }
 }

Vagrant up running for WordPress

[huupv@localhost ~]$ cd /home/huupv/project/
[huupv@localhost project]$ vagrant up

FAQs

Q1: Why use Vagrant over Docker for WordPress?

While Docker is lightweight, Vagrant provides a full virtualized environment, making it suitable for developers needing an environment closer to production.

Q2: Can I use a different Linux distribution?

Yes, replace ubuntu/bionic64 in the Vagrantfile with the desired box name from Vagrant Cloud.

Q3: How do I update the Vagrant environment?

Use the following commands:

• To apply updates: vagrant provision
• To rebuild the environment: vagrant destroy -f && vagrant up

Q4: How do I troubleshoot Vagrant errors?

• Check the Vagrant logs in the project directory.
• Refer to the Vagrant Documentation.

External Resources

• WordPress Documentation
• Vagrant Official Guide
• Apache Configuration
• MySQL Documentation

Conclusion

You have to set up a Vagrant WordPress Nginx + MariaDB. Setting up WordPress with Vagrant is a powerful way to ensure consistency and efficiency in web development. By following this guide, you can create a robust development environment tailored to your needs. Whether you’re a solo developer or part of a team, Vagrant offers the flexibility and reliability to elevate your WordPress projects. I hope will this your helpful. Thank you for reading the DevopsRoles page!