palemoon - Chromium based Java+Flash browser.mozilla-team - Stable Firefox and Mozilla Software.kubernetes - Google Kubernetes kubeadm & kubectl.google-cloud-sdk - Google Cloud Tools SDK.git-lfs - Git Large File System - removed in Linux Mint 20.gcsfuse - Google Storage gcsfuse - Mount a GCS bucket locally`.ansible - Ansible - removed in Linux Mint 20.
repo: ppa:videolan/master-daily filename: videolan custom_keys: gitignore to not override your changesīe careful not to add multiple matching files with corresponding names Custom file content If your distro is Linux Mint 20, place a file in a playbook folder with a name: mint20_custom.yaml This means - if your distro is Linux Mint 19, place a file in a playbook folder witha name: mint19_custom.yaml By default playbook will look for files: mint*.yaml If you don't want to track changes or change main variable file content with every pull, create your own custom variable files. Which folder to use when downloading and unarchivingĪre stored in mint20_tasks.yaml Custom variables, custom variable files By default taken from group_varsįorce reboot even if apt upgrade won't change anything
If set to latest, every pass of playbook will also update packages
Should we install oh-my-zsh and p10k theme Should we install extra vscode extensions Should extra deb packages should be installed If you need extra settings, instead of modyfing it, use custom variable files. Most variables are stored in mint19|20.yaml file. linux_mint.yaml -i myhost.lst -extra-vars ' ' Variables Python2 removalīe aware several packages (virtualbox-6.1, zenmap) will install python2 and remove python-is-python3 package.Īnsible-playbook. Warning - systems after upgrade will require: ansible_python_interpreter=/usr/bin/python3 setting. Make sure all apt repositories (except system ones) are removed from /etc/apt - playbook works best when this list is empty. I haven't tested it properly in case of in-place upgrade systems, so both 18=>19 and 19=>20 upgrades and playbook usage, are risky and experimental. Role of this playbook is to work on clean or cleanly-upgraded system.
by default, extra binaries (outside packages) will be installed in /usr/local/bin (adjustable by bin_path variable) If you prefer to keep them in cloud (sync between computers), down below I'll attach info how to replace binaries with proper -ymlinks (work in progress).
user specified in group_vars or passed in variable ansible_ssh_user.sudo ansible-galaxy install -r requirements.yml -roles-path /etc/ansible/roles.PermitRootLogin in /etc/ssh/sshd_config if you're using root account Sudo apt install openssh-server sudo systemctl enable ssh & sudo systemctl start ssh Sudo ansible-galaxy install -r requirements.yml Installed Linux Mint 20.0/20.1/20.2/20.3 - all 64-bit, standard options with extra codecs (available as selection during install)įor previous versions of Mint - last release supporting Linux Mint 19 was 2.1.6 Custom variables, custom variable files.Ansible playbook for your DevOps/SysOps Linux Mint 20.x based workstation.Ansible playbook for your DevOps/SysOps Linux Mint 20.x based workstation