<feed xmlns='http://www.w3.org/2005/Atom'>
<title>infra.git/roles/nginx/tasks, branch master</title>
<subtitle>Ansible playbooks for personal infrastructure.</subtitle>
<id>https://git.ilvokhin.com/infra.git/atom?h=master</id>
<link rel='self' href='https://git.ilvokhin.com/infra.git/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.ilvokhin.com/infra.git/'/>
<updated>2024-06-30T15:39:20Z</updated>
<entry>
<title>Cleanup quotes usage in YAML files</title>
<updated>2024-06-30T15:39:20Z</updated>
<author>
<name>Dmitry Ilvokhin</name>
<email>d@ilvokhin.com</email>
</author>
<published>2024-06-30T15:35:25Z</published>
<link rel='alternate' type='text/html' href='https://git.ilvokhin.com/infra.git/commit/?id=62adb64fe171ff18ff4417a710b69de256d1fdac'/>
<id>urn:sha1:62adb64fe171ff18ff4417a710b69de256d1fdac</id>
<content type='text'>
Seems quotes in YAML is a mess.

Official guidelines (see explanation here [1]) are following.

1. If you can get away without quotes, do not use them.
2. Use single quotes if you need quotes.
3. Use double quotes if you can't use single quotes for some reason.

Common reason for double quotes in this repository is line breaks for
long lines and control characters (\n, \t) in replacement patterns.

Hope, I didn't break anything.

Tested with following commands, because there are no changes in others.

$ ansible-playbook dotfiles.yml
$ ansible-playbook master.yml

[1]: https://stackoverflow.com/a/69850618/1313516
</content>
</entry>
<entry>
<title>Migrate from `yes` to `true`</title>
<updated>2024-06-30T14:31:10Z</updated>
<author>
<name>Dmitry Ilvokhin</name>
<email>d@ilvokhin.com</email>
</author>
<published>2024-06-30T14:31:10Z</published>
<link rel='alternate' type='text/html' href='https://git.ilvokhin.com/infra.git/commit/?id=049d65270e73feaa4a6729fb660e5b9aee546391'/>
<id>urn:sha1:049d65270e73feaa4a6729fb660e5b9aee546391</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Remove trailing spaces</title>
<updated>2024-06-23T19:09:26Z</updated>
<author>
<name>Dmitry Ilvokhin</name>
<email>d@ilvokhin.com</email>
</author>
<published>2024-06-23T19:09:26Z</published>
<link rel='alternate' type='text/html' href='https://git.ilvokhin.com/infra.git/commit/?id=204f497f4c2fb3dfe86a66896551c088a00536c6'/>
<id>urn:sha1:204f497f4c2fb3dfe86a66896551c088a00536c6</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Make certificate updates work for nginx</title>
<updated>2024-04-14T18:27:14Z</updated>
<author>
<name>Dmitry Ilvokhin</name>
<email>d@ilvokhin.com</email>
</author>
<published>2024-04-14T18:27:14Z</published>
<link rel='alternate' type='text/html' href='https://git.ilvokhin.com/infra.git/commit/?id=899eca5f024f22b67aa032dd82aa4393b60b85e4'/>
<id>urn:sha1:899eca5f024f22b67aa032dd82aa4393b60b85e4</id>
<content type='text'>
Currently, we obtain certificates from Let's Encrypt with standalone
mode, so when we do renew, certbot tries to run it is own webserver on
port 80, but this port is already in use by nginx.

Stop nginx, before renewal. This is quite hacky, but should work. Proper
solution is to split certificate role by standalone and non-standalone
versions.
</content>
</entry>
<entry>
<title>Swap order of nginx enablement and cert hook</title>
<updated>2024-03-31T12:50:12Z</updated>
<author>
<name>Dmitry Ilvokhin</name>
<email>d@ilvokhin.com</email>
</author>
<published>2024-03-31T12:50:12Z</published>
<link rel='alternate' type='text/html' href='https://git.ilvokhin.com/infra.git/commit/?id=283f389797b0056846580eef0f0a1729824d3e01'/>
<id>urn:sha1:283f389797b0056846580eef0f0a1729824d3e01</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Migrate to certbot hook scripts</title>
<updated>2024-03-31T11:34:38Z</updated>
<author>
<name>Dmitry Ilvokhin</name>
<email>d@ilvokhin.com</email>
</author>
<published>2024-03-31T11:34:38Z</published>
<link rel='alternate' type='text/html' href='https://git.ilvokhin.com/infra.git/commit/?id=dae57df8d747bb602ab9ef13007949b43e88df10'/>
<id>urn:sha1:dae57df8d747bb602ab9ef13007949b43e88df10</id>
<content type='text'>
Make hooks usage a bit more generic, to apply hooks for services
different from nginx.
</content>
</entry>
<entry>
<title>Configure nginx first and then enable/start</title>
<updated>2024-03-24T13:32:15Z</updated>
<author>
<name>Dmitry Ilvokhin</name>
<email>d@ilvokhin.com</email>
</author>
<published>2024-03-24T13:32:15Z</published>
<link rel='alternate' type='text/html' href='https://git.ilvokhin.com/infra.git/commit/?id=4e722e18f0014aed51fb51c130fb17ceb6f15200'/>
<id>urn:sha1:4e722e18f0014aed51fb51c130fb17ceb6f15200</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Make logrotate a dependencies for nginx</title>
<updated>2024-02-10T18:50:32Z</updated>
<author>
<name>Dmitry Ilvokhin</name>
<email>d@ilvokhin.com</email>
</author>
<published>2024-02-10T18:50:32Z</published>
<link rel='alternate' type='text/html' href='https://git.ilvokhin.com/infra.git/commit/?id=d72a4f788976fe461a1997c1bf9ca46dcc407097'/>
<id>urn:sha1:d72a4f788976fe461a1997c1bf9ca46dcc407097</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Add nginx serving directory</title>
<updated>2024-02-03T18:03:07Z</updated>
<author>
<name>Dmitry Ilvokhin</name>
<email>d@ilvokhin.com</email>
</author>
<published>2024-02-03T18:03:07Z</published>
<link rel='alternate' type='text/html' href='https://git.ilvokhin.com/infra.git/commit/?id=0e1eb77cab42206e0f0e45233425003acf6317e1'/>
<id>urn:sha1:0e1eb77cab42206e0f0e45233425003acf6317e1</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Add role for git server</title>
<updated>2024-01-21T18:14:36Z</updated>
<author>
<name>Dmitry Ilvokhin</name>
<email>d@ilvokhin.com</email>
</author>
<published>2024-01-21T18:14:36Z</published>
<link rel='alternate' type='text/html' href='https://git.ilvokhin.com/infra.git/commit/?id=e2ee37f71a5059578605c77bdd0d8bad71049c5a'/>
<id>urn:sha1:e2ee37f71a5059578605c77bdd0d8bad71049c5a</id>
<content type='text'>
The Git server role should support:
* git ssh protocol,
* git protocol,
* git smart http protocol.

Support for cgit will come as a separate role.
</content>
</entry>
</feed>
