aboutsummaryrefslogtreecommitdiff
path: root/_posts/2019-04-22-ansible-part-2.md
diff options
context:
space:
mode:
authorgabrielgio <gabriel.giovanini@pm.me>2020-07-11 22:35:14 +0200
committergabrielgio <gabriel.giovanini@pm.me>2020-07-11 22:35:14 +0200
commit60fe49ea3af38d4a7d5e8de1cdb72887b167b22d (patch)
treebb05011c311b74c7c7676b7b689bbbc2c8546c9a /_posts/2019-04-22-ansible-part-2.md
parent60b4299cb90a5b3f6e74ffd0ee0f51a0008fb3cf (diff)
downloadgabrielgio.me-60fe49ea3af38d4a7d5e8de1cdb72887b167b22d.tar.gz
gabrielgio.me-60fe49ea3af38d4a7d5e8de1cdb72887b167b22d.tar.bz2
gabrielgio.me-60fe49ea3af38d4a7d5e8de1cdb72887b167b22d.zip
Moving from jekyll to hugo
Diffstat (limited to '_posts/2019-04-22-ansible-part-2.md')
-rw-r--r--_posts/2019-04-22-ansible-part-2.md59
1 files changed, 0 insertions, 59 deletions
diff --git a/_posts/2019-04-22-ansible-part-2.md b/_posts/2019-04-22-ansible-part-2.md
deleted file mode 100644
index c5936de..0000000
--- a/_posts/2019-04-22-ansible-part-2.md
+++ /dev/null
@@ -1,59 +0,0 @@
----
-layout: post
-title: "Automating desktop setup with ansible-pull part-2"
-date: 2019-04-22
-tags: ['ansible', 'ansible-pull', 'linux', 'fedora']
----
-
-[See part 1]({% post_url 2019-03-07-ansible-part-1 %})
-
-Now we're gonna setup ansible to work with a git repository. The process is quite similar with `ansible-playbook` the only difference is that command will get a repository instead of a folder. Following the previews example we'll get vim setup automated.
-
-Do create a git repository wherever you see fit ([gitlab](https://about.gitlab.com/) and [github](https://github.com/) offer free repositories). For this task we're gonna need to add only two file: one for the `yml` file describing the tasks and the `.vimrc` file.
-
-In the `.vimrc` add your own configuration, you can see mine [over here](https://gitlab.com/gabrielgio/homestation/-/blob/debcf3458df511aef9f7dca0cb73f6cf6baddd5d/.vimrc), it is pretty simple as I don't use it but for simple text editing (like this post) so you can start with that if you don't have one.
-
-The `yml` file will have two tasks, one is to install vim itself, identical as in the part 1.
-
-{% highlight yml %}
-# main.yml
----
-- name: install vim
- dnf:
- name: vim
- state: latest
-{% endhighlight %}
-
-To copy `.vimrc` file to your `$HOME` we going to use [copy module](https://docs.ansible.com/ansible/latest/modules/copy_module.html):
-
-{% highlight yml %}
-# main.yml
----
-- name: copy vimrc file
- copy:
- src: config/.vimrc
- dest: ~/
- mode: 0644
-{% endhighlight %}
-
-After adding those two files your repository will be something [like this](https://gitlab.com/gabrielgio/homestation/-/tree/debcf3458df511aef9f7dca0cb73f6cf6baddd5d).
-
-And now we just need to run `ansible-pull` command
-
-{% highlight bash %}
-# you may need run it as a sudo
-ansible-pull -U <YOUR_REPO> -i all main.yml
-{% endhighlight %}
-
-Params:
-* `-i` is a list of hosts.
-* `-U` is the git repository url.
-
-Remember `man` is your best friend take a look at `man ansible-pull` to know more about its parameters.
-
-The best part you can quickly test and see the result by just running my sample:
-{% highlight bash %}
-ansible-pull -U https://gitlab.com/gabrielgio/homestation.git -C debcf3458df511aef9f7dca0cb73f6cf6baddd5d -i all main.yml
-{% endhighlight %}
-
-The idea here is to keep your repository as a source of truth when comes to configuration, you can add this task to your cron tab, so you just need to push something to your repository and after a few minutes not only your machine but all the machines that have it setup will receive an update. You can use this method as a simple way to install software, update machines or even distribute tools company-wise.