Skip to content
Ansible-playbook for my Fedora desktop installation
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
group_vars
roles @ da9a79b
.gitignore
.gitmodules
LICENSE
ansible.cfg
fedwise.yml
hosts
master.yml
readme.md

readme.md

fedora-desktop-ansible

This is my provisioner for the Fedora 26 Gnome3 / Wayland generic desktop. Feel free to use it, modify, contribute etc. Always interested in your comments - write me!

This repository has submodule dependency. All Ansible roles are placed in roles directory which is a git submodule.

Usage:

  1. Clone this repo
  2. Edit group_vars/all.yml
  3. Install prerequisites on destination box: dnf -y install ansible sudo python-dnf libselinux-python
  4. Create entry for your user in /etc/sudoers.d/user
  5. Enter proper ansible_ssh_host and ansible_ssh_user in hosts file
  6. Make sure it works: ansible -m ping <your_host>
  7. Rollout: ansible-playbook master.yml

Of course you may install just a specified part of the whole installation by using tags. List available tags with:

$ ansible-playbook master.yml --list-tags

And install specified part with:

$ ansible-playbook master.yml --tags dropbox,virtualbox

If you want to only update packages (like dnf update -y simply run:

$ ansible-playbook master.yml --tags pkgs,update --skip-tags install

Contributing / committing changes

  1. In order to modify those roles a bit to match your needs simply fork and work on your forked repo
  2. If you feel like your change should be added to thise repo - create Pull Request (thanks btw!)

Managing multiple desktops

I use this repository in order to manage 5+ laptops. There are two methods to achieve this multi - desktop configuration:

  1. First is to keep every workstation configuration in different branch. This way every workstation has its own master.yml and hosts file. Downside is the need for keeping branches in sync (which is a basic merge so it's not a rocket science).
  2. Second is to keep every workstation provisioner in different playbook (e.g. in plays directory). In this scenario you keep all hosts configuration in one hosts file.

Maciej Lasyk @docent-net http://maciej.lasyk.info

You can’t perform that action at this time.