foodogsquared/ansible-playbooks
1
0
Fork 0
mirror of https://github.com/foo-dogsquared/ansible-playbooks.git synced 2025-01-31 16:57:57 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
78568ab207
ansible-playbooks/roles/system/flatpak/tasks/main.yml

66 lines
1.7 KiB
YAML
Raw Normal View History

Modularize tasks into roles Now, it's becoming similar to my NixOS configuration. Not as declarative and working out of the box as it requires a server but it's the closest thing. I'll explore more configurations as I go along.
2022-03-17 09:38:44 +00:00
---
- name: Add Flatpak remotes
flatpak_remote:
state: present
name: "{{ item.name }}"
flatpakrepo_url: "{{ item.repo }}"
loop:
- name: flathub
Modularize tasks from system/base to its own role Seems like I misunderstood what tags are for. They're not individual flags for the play, they're commonly used for excluding/including tasks at runtime (e.g., `ansible-playbook $PLAYBOOK --tags $TAGS`). When running a playbook, it will execute all tasks by default. Think of them as attaching a label and letting the user choose from the playbook run. Setting multiple tags at the playbook-level seems to be the best practice as seen from jwflory's Ansible playbooks.
2022-03-19 03:18:42 +00:00
repo: https://flathub.org/repo/flathub.flatpakrepo
Modularize tasks into roles Now, it's becoming similar to my NixOS configuration. Not as declarative and working out of the box as it requires a server but it's the closest thing. I'll explore more configurations as I go along.
2022-03-17 09:38:44 +00:00
- name: flathub-beta
Modularize tasks from system/base to its own role Seems like I misunderstood what tags are for. They're not individual flags for the play, they're commonly used for excluding/including tasks at runtime (e.g., `ansible-playbook $PLAYBOOK --tags $TAGS`). When running a playbook, it will execute all tasks by default. Think of them as attaching a label and letting the user choose from the playbook run. Setting multiple tags at the playbook-level seems to be the best practice as seen from jwflory's Ansible playbooks.
2022-03-19 03:18:42 +00:00
repo: https://flathub.org/beta-repo/flathub-beta.flatpakrepo
Modularize tasks into roles Now, it's becoming similar to my NixOS configuration. Not as declarative and working out of the box as it requires a server but it's the closest thing. I'll explore more configurations as I go along.
2022-03-17 09:38:44 +00:00
- name: gnome-nightly
Modularize tasks from system/base to its own role Seems like I misunderstood what tags are for. They're not individual flags for the play, they're commonly used for excluding/including tasks at runtime (e.g., `ansible-playbook $PLAYBOOK --tags $TAGS`). When running a playbook, it will execute all tasks by default. Think of them as attaching a label and letting the user choose from the playbook run. Setting multiple tags at the playbook-level seems to be the best practice as seen from jwflory's Ansible playbooks.
2022-03-19 03:18:42 +00:00
repo: https://nightly.gnome.org/gnome-nightly.flatpakrepo
Modularize tasks into roles Now, it's becoming similar to my NixOS configuration. Not as declarative and working out of the box as it requires a server but it's the closest thing. I'll explore more configurations as I go along.
2022-03-17 09:38:44 +00:00
- name: kdeapps
Modularize tasks from system/base to its own role Seems like I misunderstood what tags are for. They're not individual flags for the play, they're commonly used for excluding/including tasks at runtime (e.g., `ansible-playbook $PLAYBOOK --tags $TAGS`). When running a playbook, it will execute all tasks by default. Think of them as attaching a label and letting the user choose from the playbook run. Setting multiple tags at the playbook-level seems to be the best practice as seen from jwflory's Ansible playbooks.
2022-03-19 03:18:42 +00:00
repo: https://distribute.kde.org/kdeapps.flatpakrepo
- name: appcenter
repo: https://flatpak.elementary.io/repo.flatpakrepo
Modularize tasks into roles Now, it's becoming similar to my NixOS configuration. Not as declarative and working out of the box as it requires a server but it's the closest thing. I'll explore more configurations as I go along.
2022-03-17 09:38:44 +00:00
- name: Install applications from 'flathub' Flatpak remote
flatpak:
state: present
name: "{{ item }}"
remote: flathub
loop:
Modularize tasks from system/base to its own role Seems like I misunderstood what tags are for. They're not individual flags for the play, they're commonly used for excluding/including tasks at runtime (e.g., `ansible-playbook $PLAYBOOK --tags $TAGS`). When running a playbook, it will execute all tasks by default. Think of them as attaching a label and letting the user choose from the playbook run. Setting multiple tags at the playbook-level seems to be the best practice as seen from jwflory's Ansible playbooks.
2022-03-19 03:18:42 +00:00
- com.github.gi_lom.dialect
Modularize tasks into roles Now, it's becoming similar to my NixOS configuration. Not as declarative and working out of the box as it requires a server but it's the closest thing. I'll explore more configurations as I go along.
2022-03-17 09:38:44 +00:00
- com.github.tchx84.Flatseal
- com.github.wwmm.easyeffects
- com.obsproject.Studio
- com.play0ad.zeroad
- com.remnantsoftheprecursors.ROTP
- com.usebottles.bottles
- com.valvesoftware.Steam
- io.github.lainsce.Emulsion
- org.blender.Blender
- org.inkscape.Inkscape
- org.kde.krita
- org.musescore.MuseScore
- org.pipewire.Helvum
- org.zrythm.Zrythm
- re.sonny.Junction
- re.sonny.Tangram
- name: Install applications from 'kdeapps' Flatpak remote
flatpak:
state: present
name: "{{ item }}"
remote: kdeapps
loop:
- org.kde.krita-nightly
- name: Install applications from 'flathub-beta' Flatpak remote
flatpak:
state: present
name: "{{ item }}"
remote: flathub-beta
loop:
- net.lutris.Lutris
- name: Install applications from 'gnome-nightly' Flatpak remote
flatpak:
state: present
name: "{{ item }}"
remote: gnome-nightly
loop:
- org.gimp.GIMP
Reference in New Issue Copy Permalink