gliech

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

Vagrant.configure("2") do |config|
  config.vm.box = "jackrayner/fedora-31-workstation"
  config.vm.provision "shell", inline: <<-EOF
    #!/usr/bin/env bash
    dnf --assumeyes --errorlevel=0 --nogpgcheck upgrade
    dnf --assumeyes --errorlevel=0 --nogpgcheck groupinstall "C Development Tools and Libraries"
    dnf --assumeyes --errorlevel=0 --nogpgcheck install git qt5-qtbase-devel qt5-qtxmlpatterns-devel qt5-linguist qt5-qtsvg-devel

gliech

#!/usr/bin/env bash
# Preface:
# There is nothing wrong with using 'if [[ $VAR == yes ]]; then' for evaluating
# internal variables. The following is mainly intended for cases where you do
# not have full control over the variable in question, like user input or envi-
# ronment variables. I am of the belief however that no one should under any
# condition use something like this:
# | VAR=true
# | if $VAR; then
# |   do_something

gliech

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

guests = [
    { name: 'ansible-old', ansible_ver: '2.6.5', verbose: false },
    { name: 'ansible-new', ansible_ver: '2.7.0', verbose: true },
]

script =  <<-SCRIPT
cat << "EOF" > playbook.yml